Vulnerability Scan Result
IP address | 185.219.169.162 |
Country | CZ |
AS number | AS204949 |
Net name | CMIS S.r.o |
80/tcp | http | nginx |
443/tcp | https | nginx |
2000/tcp | cisco-sccp | |
5060/tcp | sip |
Software / Version | Category |
---|---|
core-js 3.39.0 | JavaScript libraries |
jQuery 3.7.1 | JavaScript libraries |
Leaflet 1.9.4 | Maps |
Livefyre 1.9.4 | Comment systems |
Open Graph | Miscellaneous |
PHP 8.0.30 | Programming languages |
PWA | Miscellaneous |
Webpack | Miscellaneous |
Module Federation | Miscellaneous |
Didomi | Cookie compliance |
reCAPTCHA | Security |
Google Tag Manager | Tag managers |
HSTS | Security |
Web Application Vulnerabilities
Evidence
URL | Cookie Name | Evidence |
---|---|---|
https://mobile.www-klimatex-sk.test.sportisimo.dev/ | sm_dc | The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: sm_dc=2 |
Vulnerability description
We found that a cookie has been set without the <code>HttpOnly</code> flag, which means it can be accessed by potentially malicious JavaScript code running inside the web page. The root cause for this usually revolves around misconfigurations in the code or server settings.
Recommendation
Ensure that the HttpOnly flag is set for all cookies.
Classification
CWE | CWE-1004 |
OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
URL | Cookie Name | Evidence |
---|---|---|
https://mobile.www-klimatex-sk.test.sportisimo.dev/ | sm_dc | Set-Cookie: sm_dc=2 |
Vulnerability description
We found that a cookie has been set without the <code>Secure</code> flag, which means the browser will send it over an unencrypted channel (plain HTTP) if such a request is made. The root cause for this usually revolves around misconfigurations in the code or server settings.
Recommendation
Whenever a cookie contains sensitive information or is a session token, then it should always be passed using an encrypted channel. Ensure that the secure flag is set for cookies containing such sensitive information.
Classification
CWE | CWE-614 |
OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
Risk Level | CVSS | CVE | Summary | Affected software |
---|---|---|---|---|
5.3 | CVE-2024-5458 | In PHP versions 8.1.* before 8.1.29, 8.2.* before 8.2.20, 8.3.* before 8.3.8, due to a code logic error, filtering functions such as filter_var when validating URLs (FILTER_VALIDATE_URL) for certain types of URLs the function will result in invalid user information (username + password part of URLs) being treated as valid user information. This may lead to the downstream code accepting invalid URLs as valid and parsing them incorrectly. | php 8.0.30 |
Vulnerability description
We noticed known vulnerabilities in the target application based on the server responses. They are usually related to outdated systems and expose the affected applications to the risk of unauthorized access to confidential data and possibly denial of service attacks. Depending on the system distribution the affected software can be patched but displays the same version, requiring manual checking.
Recommendation
In order to eliminate the risk of these vulnerabilities, we recommend you check the installed software version and upgrade to the latest version.
Classification
CWE | CWE-1026 |
OWASP Top 10 - 2017 | A9 - Using Components with Known Vulnerabilities |
OWASP Top 10 - 2021 | A6 - Vulnerable and Outdated Components |
Evidence
URL | Evidence |
---|---|
https://mobile.www-klimatex-sk.test.sportisimo.dev/ | Response does not include the HTTP Content-Security-Policy security header or meta tag |
Vulnerability description
We noticed that the target application lacks the Content-Security-Policy (CSP) header in its HTTP responses. The CSP header is a security measure that instructs web browsers to enforce specific security rules, effectively preventing the exploitation of Cross-Site Scripting (XSS) vulnerabilities.
Recommendation
Configure the Content-Security-Header to be sent with each HTTP response in order to apply the specific policies needed by the application.
Classification
CWE | CWE-693 |
OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
Software / Version | Category |
---|---|
core-js 3.39.0 | JavaScript libraries |
jQuery 3.7.1 | JavaScript libraries |
Leaflet 1.9.4 | Maps |
Livefyre 1.9.4 | Comment systems |
Open Graph | Miscellaneous |
PHP 8.0.30 | Programming languages |
PWA | Miscellaneous |
Webpack | Miscellaneous |
Module Federation | Miscellaneous |
Didomi | Cookie compliance |
reCAPTCHA | Security |
Google Tag Manager | Tag managers |
HSTS | Security |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Classification
OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Vulnerability description
Website is accessible.
Vulnerability description
We have noticed that the server is missing the security.txt file, which is considered a good practice for web security. It provides a standardized way for security researchers and the public to report security vulnerabilities or concerns by outlining the preferred method of contact and reporting procedures.
Recommendation
We recommend you to implement the security.txt file according to the standard, in order to allow researchers or users report any security issues they find, improving the defensive mechanisms of your server.
Classification
OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Infrastructure Vulnerabilities
Evidence
Risk level | CVSS | CVE | Summary | Exploit |
---|---|---|---|---|
5.3 | CVE-2024-5458 | In PHP versions 8.1.* before 8.1.29, 8.2.* before 8.2.20, 8.3.* before 8.3.8, due to a code logic error, filtering functions such as filter_var when validating URLs (FILTER_VALIDATE_URL) for certain types of URLs the function will result in invalid user information (username + password part of URLs) being treated as valid user information. This may lead to the downstream code accepting invalid URLs as valid and parsing them incorrectly. | N/A |
Vulnerability description
Vulnerabilities found for PHP 8.0.30
Recommendation
We recommend you to upgrade the affected software to the latest version in order to eliminate the risks imposed by these vulnerabilities.
Evidence
Domain Queried | DNS Record Type | Description | Value |
---|---|---|---|
mobile.www-klimatex-sk.test.sportisimo.dev | A | IPv4 address | 185.219.169.162 |
Recommendation
We recommend reviewing all DNS records associated with the domain and identifying and removing unused or obsolete records.
Vulnerability description
OS detection couldn't determine the operating system.
Recommendation
Vulnerability checks are skipped for ports that redirect to another port. We recommend scanning the redirected port directly.
Evidence
Software / Version | Category |
---|---|
PHP 8.0.30 | Programming languages |
reCAPTCHA | Security |
HSTS | Security |
Webpack | Miscellaneous |
Module Federation | Miscellaneous |
Google Tag Manager | Tag managers |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.