Socrates-Pentest

CertiKCode version: not recorded (see the report)

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

CertiK reviewed Socrates (Socrates-Pentest) on 31 Jul 2023: 10 findings, 0 critical; 3 acknowledged, 7 open.

No open critical findings
Open the reportOpen Socrates’s security record

Report hosted on skynet.certik.com.

Trustblock does not review code.

Findings10

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

SeverityOpenAcknowledgedFixed
Critical000
High020
Medium010
Low700
LowMisconfigured CORS PolicyOpen

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

LowMissing Cookie Security FlagsOpen

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

LowMissing Security HeadersOpen

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.

LowUser Enumeration in LoginOpen

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`.

LowVerbose error messageOpen

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.

LowWeak TLS configurationOpen

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.

LowWeb server information disclosureOpen

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`

Contracts in scope

No deployed address is recorded for this audit.

The report names a repository or files. Open the report to see its scope.

Part of Socrates’s security record

Socrates
Audits1 audit by 1 firmLast audit Oct 2023, by CertiK.
Critical findingsNo open critical findingsIn 1 report.
Open Socrates’s security record

Security firm

CertiK

1,045 projects reviewed · 1,376 reports · latest May 2025

See CertiK’s audits

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