Vulnerability Scan Result
| Title: | No title found |
| Description: | No description found |
| IP address | 67.198.205.86 |
| Country | US  |
| AS number | AS35908 |
| Net name | Krypt Technologies |
No open ports were found.
| Software / Version | Category |
|---|---|
| CentOS | Operating systems |
| Apache HTTP Server 2.4.62 | Web servers |
| OpenSSL 3.2.2 | Web server extensions |
| PHP 7.4.33 | Programming languages |
Web Application Vulnerabilities
Evidence
| Risk Level | CVSS | CVE | Summary | Affected software |
|---|---|---|---|---|
| 6.2 | CVE-2022-4900 | A vulnerability was found in PHP where setting the environment variable PHP_CLI_SERVER_WORKERS to a large value leads to a heap buffer overflow. | php 7.4.33 | |
| 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 7.4.33 |
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.
Risk description
The risk is that an attacker could search for an appropriate exploit (or create one himself) for any of these vulnerabilities and use it to attack the system. Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed 'high' severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.
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 | Response URL | Evidence |
|---|---|---|
| http://qsadv.rigaprecast.com/bhyor158kgshgu9rl2RVGU4UVh3QzFWTXRKNnFvOGJXMWEtMzE5NC0yNjczNTE1Mi0wZmVmMDI3MS00OTcyLTE4cFNsRTFNOWgwcTZ5d3NHSGJa/yhnfutft8bmyl/OffoeN4ZIYKH4Lw2TorAy7Lz/542426 | http://qsadv.rigaprecast.com/bhyor158kgshgu9rl2RVGU4UVh3QzFWTXRKNnFvOGJXMWEtMzE5NC0yNjczNTE1Mi0wZmVmMDI3MS00OTcyLTE4cFNsRTFNOWgwcTZ5d3NHSGJa/yhnfutft8bmyl/OffoeN4ZIYKH4Lw2TorAy7Lz/542426 | Communication is made over unsecure, unencrypted HTTP. |
Vulnerability description
We noticed that the communication between the web browser and the server is done using the HTTP protocol, which transmits data unencrypted over the network.
Risk description
The risk is that an attacker who manages to intercept the communication at the network level can read and modify the data transmitted (including passwords, secret tokens, credit card information and other sensitive data).
Recommendation
We recommend you to reconfigure the web server to use HTTPS - which encrypts the communication between the web browser and the server.
Classification
| CWE | CWE-311 |
| OWASP Top 10 - 2017 | A3 - Sensitive Data Exposure |
| OWASP Top 10 - 2021 | A4 - Insecure Design |
Evidence
| URL | Evidence |
|---|---|
| http://qsadv.rigaprecast.com/bhyor158kgshgu9rl2RVGU4UVh3QzFWTXRKNnFvOGJXMWEtMzE5NC0yNjczNTE1Mi0wZmVmMDI3MS00OTcyLTE4cFNsRTFNOWgwcTZ5d3NHSGJa/yhnfutft8bmyl/OffoeN4ZIYKH4Lw2TorAy7Lz/542426 | Response headers do not include the Referrer-Policy HTTP security header as well as the |
Vulnerability description
We noticed that the target application's server responses lack the Referrer-Policy HTTP header, which controls how much referrer information the browser will send with each request originated from the current web application.
Risk description
The risk is that if a user visits a web page (e.g. "http://example.com/pricing/") and clicks on a link from that page going to e.g. "https://www.google.com", the browser will send to Google the full originating URL in the `Referer` header, assuming the Referrer-Policy header is not set. The originating URL could be considered sensitive information and it could be used for user tracking.
Recommendation
The Referrer-Policy header should be configured on the server side to avoid user tracking and inadvertent information leakage. The value `no-referrer` of this header instructs the browser to omit the Referer header entirely.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
| URL | Evidence |
|---|---|
| http://qsadv.rigaprecast.com/bhyor158kgshgu9rl2RVGU4UVh3QzFWTXRKNnFvOGJXMWEtMzE5NC0yNjczNTE1Mi0wZmVmMDI3MS00OTcyLTE4cFNsRTFNOWgwcTZ5d3NHSGJa/yhnfutft8bmyl/OffoeN4ZIYKH4Lw2TorAy7Lz/542426 | 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.
Risk description
The risk is that if the target application is vulnerable to XSS, lack of this header makes it easily exploitable by attackers.
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 |
|---|---|
| CentOS | Operating systems |
| Apache HTTP Server 2.4.62 | Web servers |
| OpenSSL 3.2.2 | Web server extensions |
| PHP 7.4.33 | Programming languages |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
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 |
Evidence
Vulnerability description
Website is accessible.
Evidence
| URL | Method | Summary |
|---|---|---|
| http://qsadv.rigaprecast.com/bhyor158kgshgu9rl2RVGU4UVh3QzFWTXRKNnFvOGJXMWEtMzE5NC0yNjczNTE1Mi0wZmVmMDI3MS00OTcyLTE4cFNsRTFNOWgwcTZ5d3NHSGJa/yhnfutft8bmyl/OffoeN4ZIYKH4Lw2TorAy7Lz/542426 | OPTIONS | We did a HTTP OPTIONS request. The server responded with a 405 status code and the header: `Allow: GET` Request / Response |
Vulnerability description
We have noticed that the webserver responded with an Allow HTTP header when an OPTIONS HTTP request was sent. This method responds to requests by providing information about the methods available for the target resource.
Risk description
The only risk this might present nowadays is revealing debug HTTP methods that can be used on the server. This can present a danger if any of those methods can lead to sensitive information, like authentication information, secret keys.
Recommendation
We recommend that you check for unused HTTP methods or even better, disable the OPTIONS method. This can be done using your webserver configuration.
Classification
| CWE | CWE-16 |
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Infrastructure Vulnerabilities
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| qsadv.rigaprecast.com | A | IPv4 address | 67.198.205.86 |
Risk description
An initial step for an attacker aiming to learn about an organization involves conducting searches on its domain names to uncover DNS records associated with the organization. This strategy aims to amass comprehensive insights into the target domain, enabling the attacker to outline the organization's external digital landscape. This gathered intelligence may subsequently serve as a foundation for launching attacks, including those based on social engineering techniques. DNS records pointing to services or servers that are no longer in use can provide an attacker with an easy entry point into the network.
Recommendation
We recommend reviewing all DNS records associated with the domain and identifying and removing unused or obsolete records.