Socrates audit reports

Arbitrum, BNB Chain, Ethereum, Polygon (POS)socrates.comXGitHub

Socrates has 1 public audit report from CertiK; dated 4 Oct 2023; no critical findings reported.

Critical findings
No open critical findings
In 1 report.
Open the latest report
Your label, live
Get the label for your site

Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.

Open findings across every firm16

Statuses are the security firms’ own

16 findings are still open or acknowledged in the firms’ reports: 4 high, 2 medium, 10 low (10 open, 6 acknowledged).

High
4
Medium
2
Low
10
  • High Acknowledged

    Centralization Related Risks

    Socrates v2 Audit · CertiK · 4 Oct 2023 · Report ↗

  • High Acknowledged

    Centralized Control of Contract Upgrade

    Socrates v2 Audit · CertiK · 4 Oct 2023 · Report ↗

  • High Acknowledged

    Broken 'Login with Email' feature

    Socrates-Pentest · CertiK · 31 Jul 2023 · Report ↗

  • High Acknowledged

    Code verification can be sent to arbitrary email

    Socrates-Pentest · CertiK · 31 Jul 2023 · Report ↗

  • Medium Acknowledged

    Not Recommended MetadataURI Protocol

    Socrates v2 Audit · CertiK · 4 Oct 2023 · Report ↗

  • Medium Acknowledged

    Arbitrary Wallet Register

    Socrates-Pentest · CertiK · 31 Jul 2023 · Report ↗

  • Low Open

    Lack of Storage Gap in Upgradeable Contract

    Socrates v2 Audit · CertiK · 4 Oct 2023 · Report ↗

  • Low Open

    Potential Cross-Chain Replay Attack

    Socrates v2 Audit · CertiK · 4 Oct 2023 · Report ↗

  • Low Open

    Unnecessary Storage Read Access in For Loop

    Socrates v2 Audit · CertiK · 4 Oct 2023 · Report ↗

  • Low Open

    Misconfigured CORS Policy

    Socrates-Pentest · CertiK · 31 Jul 2023 · Report ↗

All 16 open and acknowledged findings

Audits1

Newest first

1 other security report listed, not counted

ReportSecurity firmDateScopeCritical findingsFindingsSource
Socrates v2 AuditSecurity firm: CertiKDate: Scope: Files listedNone openFindings: 2 high · 1 medium · 3 low
3 acknowledged · 3 open
skynet.certik.com ↗
Socrates-Pentest

Penetration test of off-chain systemsNot counted as an audit report

Security firm: CertiKDate: Scope: Not recorded; see the reportNone openFindings: 2 high · 1 medium · 7 low
3 acknowledged · 7 open
skynet.certik.com ↗

Findings16

Statuses are the security firm’s own, from each report.

SeverityOpenAcknowledgedFixed
Critical000
High040
Medium020
Low1000
LowLack of Storage Gap in Upgradeable ContractSocrates v2 Audit · CertiK · 4 Oct 2023Open

There is no storage gap preserved in the `ExternalEarlyBird` base contract. Any logic contract that acts as a base contract that needs to be inherited by other upgradeable child should have a reasonable size of storage gap preserved for the new state variable introduced by the future upgrades.

Open the report
LowPotential Cross-Chain Replay AttackSocrates v2 Audit · CertiK · 4 Oct 2023Open

Signed messages are not properly verified with the current chain ID, thus allowing attackers to perform replay attacks across chains. Hardcoded or cached chain ID values are also vulnerable since a hard fork may occur and change the chain ID in the future. ```solidity=50 require(signerAddress == ecrecover(messageDigest, v, r, s), "Socrates: Signature mismatch"); ``` - Calling `ecrecover` with a hash that does not properly include the chain ID.

Open the report
LowUnnecessary Storage Read Access in For LoopSocrates v2 Audit · CertiK · 4 Oct 2023Open

The for loop contains repeated storage read access in the condition check. Given that the ending condition does not change in the for loop, the repeated storage read is unnecessary, and its associated high gas cost can be eliminated. ```solidity=76 for (uint256 i = 1; i < portions.length; i++) { ``` Loop condition `i < portions.length` accesses the `length` field of a storage array. --- ```solidity=103 for (uint256 i = 0; i < portions.length; i++) { ``` Loop condition `i < portions.length` accesses the `length` field of a storage array.

Open the report
LowMisconfigured CORS PolicySocrates-Pentest · CertiK · 31 Jul 2023Open

During the test, it was found that the HTTP response from the server reflect an arbitrary origin in the "Access- Control-Allow-Origin" header.

Open the report
LowMissing Cookie Security FlagsSocrates-Pentest · CertiK · 31 Jul 2023Open

The session cookie `QA-ADMIN-TOEKN` is not properly protected by the "HTTPOnly", "Secure" and "SameSite" attributes.

Open the report
LowMissing Security HeadersSocrates-Pentest · CertiK · 31 Jul 2023Open

HTTP headers are well known and their implementation can make your application more versatile and secure. Modern browsers support many HTTP headers that can improve web application security to protect against clickjacking, cross-site scripting, and other common attacks. The important ones are missing and should be added to the response headers. They are listed below. - `Content-Security-Policy`: Content Security Policy is an effective measure to protect your site from XSS attacks. By whitelisting sources of approved content, you can prevent the browser from loading malicious assets. - `X-Frame-Options`: X-Frame-Options tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking. Recommended value "X-Frame-Options: SAMEORIGIN". - `X-Content-Type-Options`: X-Content-Type-Options stops a browser from trying to MIME-sniff the content type and forces it to stick with the declared content-type. The only valid value for this header is "X-Content-Type-Options: nosniff". - `Referrer-Policy`: Referrer Policy is a new header that allows a site to control how much information the browser includes with navigations away from a document and should be set by all sites. - `Permissions-Policy`: Permissions Policy is a new header that allows a site to control which features and APIs can be used in the browser. - `HTTP Strict Transport Security` (also named HSTS) is an opt-in security enhancement that is specified by a web application through the use of a special response header. Once a supported browser receives this header that browser will prevent any communications from being sent over HTTP to the specified domain and will instead send all communications over HTTPS. It also prevents HTTPS click through prompts on browsers. - `Cache-Control`: This header holds directives (instructions) for caching in both requests and responses. If a given directive is in a request, it does not mean this directive is in the response Note that not all headers will be relevant for each endpoint, but security best practices stipulate that these headers should be set for all server responses, regardless of content.

Open the report
LowUser Enumeration in LoginSocrates-Pentest · CertiK · 31 Jul 2023Open

The `Login` functionality allows an attacker to infer if a username is registered on the platform based on the server response. When an invalid username is sent to the server, the server responds with `用户不存在`. Also the `code` parameter is `900011` and includes the parameter `time`. If the user is valid, the server responds with `用户名或密码错误` and code `10101`. In that case, the response does not includes the parameter `time`.

Open the report
LowVerbose error messageSocrates-Pentest · CertiK · 31 Jul 2023Open

The API response with an error message when receiving an invalid data type. The errors are related to data type conversion, for example from String to Long.

Open the report
LowWeak TLS configurationSocrates-Pentest · CertiK · 31 Jul 2023Open

The remote service accepts connections encrypted using TLS 1.0. TLS 1.0 has a number of cryptographic design flaws. Modern implementations of TLS 1.0 mitigate these problems, but newer versions of TLS like 1.2 and 1.3 are designed against these flaws and should be used whenever possible. As of March 31, 2020, Endpoints that aren’t enabled for TLS 1.2 and higher will no longer function properly with major web browsers and major vendors. PCI DSS v3.2 requires that TLS 1.0 be disabled entirely by June 30, 2018, except for POS POI terminals (and the SSL/TLS termination points to which they connect) that can be verified as not being susceptible to any known exploits.

Open the report
LowWeb server information disclosureSocrates-Pentest · CertiK · 31 Jul 2023Open

The web application `https://test.actqa.com/` exposes information about the software version used by the web server through the `Server` header in the HTTP response. - `Server: nginx/1.22.0` In addition, the admin interface on `https://testop.actqa.com/` expose the server software through the `X-Powered-By` HTTP header. - `X-Powered-By: Express`

Open the report

Contracts

No deployed address is recorded for these audits.

The reports name a repository or files. Open a report to see its scope.

The repositories and files the reports name

Socrates: questions

Is Socrates audited?

Trustblock holds 1 public audit report for Socrates, dated 4 Oct 2023. The latest is by CertiK (“Socrates v2 Audit”).

Who audited Socrates?

CertiK wrote the report Trustblock holds for Socrates.

Are there open findings in Socrates’s audits?

16 findings are still open or acknowledged in the firms’ reports: 4 high, 2 medium, 10 low (10 open, 6 acknowledged). No critical finding is reported. Statuses are the security firms’ own.

Show this on your site

Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.

Content

Facts

Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.

Fixed as
Language

Style

Layout
Theme
Accent
Corners

Format

Size
Date
Embed as
HTML
<head>
<script src="https://widget.trustblock.run/project-widget.min.js" defer></script>
</head>
<body>
<div
data-tb-project-widget
data-tb-project-slug="socrates"
></div>
</body>

Paste the code where the label should appear. It uses no API credit and updates by itself.

Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.

Tell us