Vulnerability Scan Result
| Title: | Dream Singles is the Premier International Dating Site With The Most Beautiful Women Abroad |
| Description: | Dream Singles is a premium international dating website connecting singles from around the world. Trusted Since 2003. Voted top niche dating site. Confirmed Profiles Only. 100% Free to Join. |
| ip_address | 209.170.79.82 |
| country | US  |
| network_name | Arelion Sweden Ab |
| asn | AS1299 |
| ip_address | 209.170.79.83 |
| country | US |
| network_name | Arelion Sweden Ab |
| asn | AS1299 |
22/tcp | ssh | OpenSSH 8.9p1 Ubuntu 3ubuntu0.13 |
80/tcp | http | - - |
443/tcp | https | - - |
8080/tcp | http | - - |
| Software / Version | Category |
|---|---|
| Aimtell | Marketing automation |
| Amazon Web Services | PaaS |
| Amazon S3 | CDN |
| Bootstrap 4.6.2 | UI frameworks |
| Google Analytics | Analytics |
| Nginx | Web servers, Reverse proxies |
| PayPal | Payment processors |
| Webpack | Miscellaneous |
| DigiCert | SSL/TLS certificate authorities |
| Google Tag Manager | Tag managers |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://www.dream-singles.com/aboutUs | ds_SESSION_a7840268c8139bc11242b3fd43dba539 | Set-Cookie: .dream-singles.com |
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 | Cookie Name | Evidence |
|---|---|---|
| https://www.dream-singles.com/aboutUs | ds_SESSION_a7840268c8139bc11242b3fd43dba539 | Set-Cookie: ds_SESSION_a7840268c8139bc11242b3fd43dba539=0vqj4525icarfj7po8u63fj8f5 |
Vulnerability description
We found that a cookie has been set without the Secure 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.
Risk description
The risk exists that an attacker will intercept the clear-text communication between the browser and the server and he will steal the cookie of the user. If this is a session cookie, the attacker could gain unauthorized access to the victim's web session.
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 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://www.dream-singles.com/aboutUs | 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://www.dream-singles.com/aboutUs | 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
| Software / Version | Category |
|---|---|
| Aimtell | Marketing automation |
| Amazon Web Services | PaaS |
| Amazon S3 | CDN |
| Bootstrap 4.6.2 | UI frameworks |
| Google Analytics | Analytics |
| Nginx | Web servers, Reverse proxies |
| PayPal | Payment processors |
| Webpack | Miscellaneous |
| DigiCert | SSL/TLS certificate authorities |
| 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.
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
Vulnerability description
We found the robots.txt on the target server. This file instructs web crawlers what URLs and endpoints of the web application they can visit and crawl. Website administrators often misuse this file while attempting to hide some web pages from the users.
Risk description
There is no particular security risk in having a robots.txt file. However, it's important to note that adding endpoints in it should not be considered a security measure, as this file can be directly accessed and read by anyone.
Recommendation
We recommend you to manually review the entries from robots.txt and remove the ones which lead to sensitive locations in the website (ex. administration panels, configuration files, etc).
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
| CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
|---|---|---|---|---|---|
| CVE-2024-6531 | 6.4 | 0.00072 | 0.22588 | No | A vulnerability has been identified in Bootstrap that exposes users to Cross-Site Scripting (XSS) attacks. The issue is present in the carousel component, where the data-slide and data-slide-to attributes can be exploited through the href attribute of an <a> tag due to inadequate sanitization. This vulnerability could potentially enable attackers to execute arbitrary JavaScript within the victim's browser. |
Vulnerability description
Vulnerabilities found for Bootstrap 4.1.3
Risk description
These vulnerabilities expose the affected applications to the risk of unauthorized access to confidential data and possibly to denial of service attacks. An attacker could search for an appropriate exploit (or create one) for any of these vulnerabilities and use it to attack the system. Notes: - The vulnerabilities are identified based on the server's version.; - Only the first 5 vulnerabilities with the highest risk are shown for each port.; 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
We recommend you to upgrade the affected software to the latest version in order to eliminate the risks imposed by these vulnerabilities.
Evidence
We found insecure EDNS configuration on the following nameservers: ns-138.awsdns-17.com ns-138.awsdns-17.com:
Vulnerability description
We found that the server does not properly implement EDNS (Extension Mechanisms for DNS). EDNS allows larger DNS packets and supports modern features such as DNSSEC.
Risk description
The risk exists because improper or missing EDNS support can lead to truncated responses, degraded DNS performance, and compatibility issues with DNSSEC. This exposes users to risks such as incomplete DNS resolution and failed DNSSEC validation.
Recommendation
We recommend ensuring the proper implementation of EDNS on the DNS server. Update the DNS server software to support EDNS fully, including modern features like DNSSEC. Regularly test DNS configurations to ensure compliance and performance.
Evidence
We found insecure DNS cookie usage on the following nameservers: ns-138.awsdns-17.com, ns-1515.awsdns-61.org, ns-1917.awsdns-47.co.uk, ns-817.awsdns-38.net
Vulnerability description
We found that the server does not implement DNS Cookies or uses them insecurely. DNS Cookies help prevent DNS-based attacks, such as spoofing and amplification attacks.
Risk description
The risk exists because without DNS Cookies, the server is vulnerable to DNS spoofing and amplification attacks. Attackers can manipulate responses or use the server in distributed denial-of-service (DDoS) attacks, compromising network availability and security.
Recommendation
We recommend enabling DNS Cookies to prevent spoofed DNS responses. Ensure proper cookie validation is implemented to mitigate DNS amplification attacks. Regularly update DNS servers to support the latest DNS security features.
Evidence
| Operating System | Accuracy |
|---|---|
| Linux 3.2 - 3.8 | 89% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| Bootstrap 4.1.3 | UI frameworks |
| Nginx | Web servers, Reverse proxies |
| Amazon Web Services | PaaS |
| Cloudflare | CDN |
| reCAPTCHA | Security |
| jsDelivr | CDN |
| jQuery 3.5.1 | JavaScript libraries |
| Google Tag Manager | Tag managers |
| cdnjs | CDN |
| Amazon S3 | CDN |
| Aimtell | Marketing automation |
| Google Analytics | Analytics |
| HSTS | Security |
| DigiCert | SSL/TLS certificate authorities |
| Popper 1.12.9 | Miscellaneous |
| Webpack | Miscellaneous |
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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| www.dream-singles.com | A | IPv4 address | 209.170.79.82 |
| www.dream-singles.com | A | IPv4 address | 209.170.79.83 |
| www.dream-singles.com | NS | Name server | ns-138.awsdns-17.com |
| www.dream-singles.com | NS | Name server | ns-1515.awsdns-61.org |
| www.dream-singles.com | NS | Name server | ns-1917.awsdns-47.co.uk |
| www.dream-singles.com | NS | Name server | ns-817.awsdns-38.net |
| www.dream-singles.com | MX | Mail server | 1 aspmx.l.google.com |
| www.dream-singles.com | MX | Mail server | 10 aspmx2.googlemail.com |
| www.dream-singles.com | MX | Mail server | 10 aspmx3.googlemail.com |
| www.dream-singles.com | MX | Mail server | 5 alt1.aspmx.l.google.com |
| www.dream-singles.com | MX | Mail server | 5 alt2.aspmx.l.google.com |
| www.dream-singles.com | SOA | Start of Authority | ns-1515.awsdns-61.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400 |
| www.dream-singles.com | TXT | Text record | "abuseipdb-verification=ovjcGPo0" |
| www.dream-singles.com | TXT | Text record | "google-site-verification=H23c4qIJM3nge96CboyE99V47rXve-JyN4kIP2vVpng" |
| www.dream-singles.com | TXT | Text record | "google-site-verification=s9rpPWfRCAwPAL-yvxIBdG64JVSCRZNfbb5XfLMCfcE" |
| www.dream-singles.com | CNAME | Canonical name | dream-singles.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.