Vulnerability Scan Result
| Title: | No title found |
| Description: | No description found |
| ip_address | 13.36.181.152 |
| country | FR  |
| network_name | Amazon Inc |
| asn | AS16509 |
| ip_address | 13.36.130.82 |
| country | FR |
| network_name | Amazon Inc |
| asn | AS16509 |
| ip_address | 15.188.222.242 |
| country | FR |
| network_name | Amazon Inc |
| asn | AS16509 |
80/tcp | http | - - |
443/tcp | https | - - |
No technologies could be detected.
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://s3s-main.net/fw19c3/40654651/5793/4087612468.html | cloudmedia_v2 | Set-Cookie: .s3s-main.net |
Vulnerability description
We found that the target application sets cookies with a domain scope that is too broad. Specifically, cookies intended for use within a particular application are configured in such a way that they can be accessed by multiple subdomains of the same primary domain.
Risk description
The risk is that a cookie set for example.com may be sent along with the requests sent to dev.example.com, calendar.example.com, hostedsite.example.com. Potentially risky websites under your main domain may access those cookies and use the victim session from the main site.
Recommendation
The `Domain` attribute should be set to the origin host to limit the scope to that particular server. For example if the application resides on server app.mysite.com, then it should be set to `Domain=app.mysite.com`
Classification
| CWE | CWE-614 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://s3s-main.net/fw19c3/40654651/5793/4087612468.html | 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 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://s3s-main.net/fw19c3/40654651/5793/4087612468.html | Response headers do not include the X-Content-Type-Options HTTP security header |
Vulnerability description
We noticed that the target application's server responses lack the X-Content-Type-Options header. This header is particularly important for preventing Internet Explorer from reinterpreting the content of a web page (MIME-sniffing) and thus overriding the value of the Content-Type header.
Risk description
The risk is that lack of this header could make possible attacks such as Cross-Site Scripting or phishing in Internet Explorer browsers.
Recommendation
We recommend setting the X-Content-Type-Options header such as `X-Content-Type-Options: nosniff`.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://s3s-main.net/fw19c3/40654651/5793/4087612468.html | 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 | |
| OWASP Top 10 - 2021 |
Evidence
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.
Risk description
There is no particular risk in not having a security.txt file for your server. However, this file is important because it offers a designated channel for reporting vulnerabilities and security issues.
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.
Infrastructure Vulnerabilities
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| s3s-main.net | SPF | Sender Policy Framework | "spf2.0/mfrom,pra include:spf2.splio.com -all" |
| s3s-main.net | SPF | Sender Policy Framework | "v=spf1 include:spf.splio.com -all" |
| s3s-main.net | SPF | Sender Policy Framework | "v=spf1 include:spf.splio.com -all" |
Vulnerability description
We found that the target has more than one configured DNS SPF (Sender Policy Framework) record. SPF is designed to prevent email spoofing by specifying which mail servers are allowed to send email on behalf of a domain. According to RFC 7208, a domain must have only one SPF record. Multiple SPF records can cause validation issues, leading to failed email authentication checks. This could impact email deliverability, and legitimate emails may be rejected or marked as spam.
Risk description
Having multiple SPF records poses a significant risk to email security and deliverability. When a receiving email server encounters more than one SPF record, it might fail to properly validate the SPF configuration, leading to the rejection of legitimate emails or their classification as spam. This can negatively affect business operations by disrupting email communication with customers, partners, or internal stakeholders. Furthermore, failure to comply with SPF best practices can make the domain more vulnerable to email spoofing attacks, which could damage the organization's reputation and lead to phishing attempts using the domain name.
Recommendation
We recommend removing any redundant or conflicting SPF records and ensuring that only one SPF record is present. The multiple records should be merged into a single SPF entry that includes all necessary authorized mail servers. For example, if two SPF records exist, they can be combined into one as follows:\nv=spf1 include:spf1.example.com include:spf2.example.com -all\nAfterward, verify that the single SPF record covers all the intended mail servers. Test the SPF configuration using email testing tools to confirm that it works correctly and that email deliverability is not negatively impacted.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.s3s-main.net | TXT | Text record | "v=DMARC1; p=reject; sp=reject; pct=100; rua=mailto:dmarc@tech.splio.com" |
Vulnerability description
We found that the DMARC record for the domain is not configured with ruf tag. A missing ruf (forensic reporting) tag in a DMARC record indicates that the domain owner has not enabled the collection of detailed failure reports. Forensic reports provide valuable insights into specific instances where emails fail DMARC authentication. Without the ruf tag, the domain administrator loses the ability to receive and analyze these reports, making it difficult to investigate individual email failures or identify targeted phishing or spoofing attacks that may be exploiting weaknesses in the email authentication setup.
Risk description
Without forensic reports (ruf), domain owners have limited visibility into the specifics of failed DMARC validation. This means potential malicious activity, such as email spoofing or phishing attempts, might go unnoticed until they result in more significant security breaches or reputational damage. Forensic reports allow for quick response to email abuses by providing detailed information about the failure, including the header information of the emails involved. The absence of this data hampers an organization's ability to identify and mitigate threats targeting its domain, increasing the risk of ongoing spoofing and fraud.
Recommendation
We recommend configuring the ruf tag in the DMARC record. This tag specifies where forensic reports should be sent, providing the domain owner with detailed data on DMARC validation failures. Forensic reports allow administrators to analyze why certain emails failed authentication, making it easier to fine-tune DMARC policies or address potential vulnerabilities. Ensure that the ruf email address belongs to a secure and trusted location capable of handling sensitive email data.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| s3s-main.net | A | IPv4 address | 13.36.181.152 |
| s3s-main.net | A | IPv4 address | 13.36.130.82 |
| s3s-main.net | A | IPv4 address | 15.188.222.242 |
| s3s-main.net | NS | Name server | ns0.splio.name |
| s3s-main.net | NS | Name server | ns1.splio.name |
| s3s-main.net | NS | Name server | ns2.splio.name |
| s3s-main.net | NS | Name server | ns3.splio.name |
| s3s-main.net | MX | Mail server | 10 bounce.splio4.com |
| s3s-main.net | SOA | Start of Authority | ns0.splio.name. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400 |
| s3s-main.net | TXT | Text record | "google-site-verification=aDW_QQMjQZX3m1zVq5jLPUtp0ENR5QxYugR85xjKTHo" |
| s3s-main.net | TXT | Text record | "google-site-verification=g4FREaChiJ6T3B8edpuTgQx6j1Q5YbnOT0sD_cC3t8g" |
| s3s-main.net | TXT | Text record | "google-site-verification=jt2GzyzjjJXPM1sldeaPZbQxSoBoP9rlQXCU9vKDYxA" |
| s3s-main.net | TXT | Text record | "google-site-verification=maZcYpvHCa4mi2b-5r1D3EEcWf-E1TQVGdRJbnIlcjc" |
| s3s-main.net | TXT | Text record | "spf2.0/mfrom,pra include:spf2.splio.com -all" |
| s3s-main.net | TXT | Text record | "yahoo-verification-key=sAPg9PGDOwBQev+rJAFCeOBpFQKGWvvI7Noi79eXyNo=" |
| s3s-main.net | SPF | Sender Policy Framework | "spf2.0/mfrom,pra include:spf2.splio.com -all" |
| s3s-main.net | SPF | Sender Policy Framework | "v=spf1 include:spf.splio.com -all" |
| s3s-main.net | SPF | Sender Policy Framework | "v=spf1 include:spf.splio.com -all" |
| _dmarc.s3s-main.net | TXT | Text record | "v=DMARC1; p=reject; sp=reject; pct=100; rua=mailto:dmarc@tech.splio.com" |
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.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| s3s-main.net | SPF | Sender Policy Framework | "spf2.0/mfrom,pra include:spf2.splio.com -all" |
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| s3s-main.net | SPF | Sender Policy Framework | "v=spf1 include:spf.splio.com -all" |
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| s3s-main.net | SPF | Sender Policy Framework | "v=spf1 include:spf.splio.com -all" |
Evidence
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| dkim02 | rsa | 1296 | "k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDFG63OUQU+COcURv/5/rD5MLkAh3mS8c2JqskStBgMJiPTfQaxIc+qqtZAVkiud4jO5SQ5plnvRYtMnfSe+VoyGiz1j/3x5i4PUjiFKLKiGnTpvW7LcrpWwVgeRnUAqeIvACnlTc9uXv30moMvPNq4qPe1bD05oDvpxJHa12lqlwIDAQAB" |
Evidence
| Software / Version | Category |
|---|---|
| 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.
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.
Evidence
| Software / Version | Category |
|---|---|
| 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.
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.