Vulnerability Scan Result
| Title: | Safe&Sound Removals & Transport | Professional Moving Services - Berlin |
| Description: | Reliable and affordable removal services. |
| ip_address | 83.168.99.244 |
| country | PL  |
| network_name | NODEA Sp. z o.o. |
| asn | AS214349 |
80/tcp | http | OpenResty web app server 1.27.1.1 |
443/tcp | https | OpenResty web app server 1.27.1.1 |
2082/tcp | http | OpenResty web app server 1.27.1.1 |
2083/tcp | https | nginx - |
2086/tcp | http | OpenResty web app server 1.27.1.1 |
| Software / Version | Category |
|---|---|
| Nginx | Web servers, Reverse proxies |
| OpenResty 1.27.1.1 | Web servers |
Web Application Vulnerabilities
Evidence
| URL | Evidence |
|---|---|
| https://safeandsoundremovals.co.uk/ | 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://safeandsoundremovals.co.uk/ | 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 |
|---|---|
| Nginx | Web servers, Reverse proxies |
| OpenResty 1.27.1.1 | Web servers |
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
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://safeandsoundremovals.co.uk/ | Response headers do not include the HTTP Strict-Transport-Security header |
Vulnerability description
We noticed that the target application lacks the HTTP Strict-Transport-Security header in its responses. This security header is crucial as it instructs browsers to only establish secure (HTTPS) connections with the web server and reject any HTTP connections.
Risk description
The risk is that lack of this header permits an attacker to force a victim user to initiate a clear-text HTTP connection to the server, thus opening the possibility to eavesdrop on the network traffic and extract sensitive information (e.g. session cookies).
Recommendation
The Strict-Transport-Security HTTP header should be sent with each HTTPS response. The syntax is as follows: `Strict-Transport-Security: max-age=<seconds>[; includeSubDomains]` The parameter `max-age` gives the time frame for requirement of HTTPS in seconds and should be chosen quite high, e.g. several months. A value below 7776000 is considered as too low by this scanner check. The flag `includeSubDomains` defines that the policy applies also for sub domains of the sender of the response.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://safeandsoundremovals.co.uk/ | 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-1021 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Infrastructure Vulnerabilities
Evidence
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| default | rsa | 1422 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsXujVq8QjS4ZInx1f5aAnR+swAP9EGzOJ3v/cUizUps3hujTXelb8rrUhO3M7+jpQpQMofX0OMPGIEpi61UO9i0hLvFi7MLRnZjuVPcl19RjSbDn3KKe7EtAVfP4nmmcjgu0f4j+UrmyaTRC73MJy443zHwxdQPqujNTDIfqKRuRiwRn877zeP+SktllPVA97" "h3DgPBzxne5wGHI4VEsgLdtw7+0kMvxUGhmLQUxRlTbCKGOm+XCF43ztueUXFYPsoEU/y7d6GSsZH1u7fXp80N8AsbuCVMJwXTIM76k2tJggok2iVfyo8bzFO5KpRwHZ1Y75scAvKMYDOmyDvFbXwIDAQAB;" |
Vulnerability description
We found that the DKIM record uses common selectors. The use of common DKIM selectors such as default, test, dkim, or mail may indicate a lack of proper customization or key management. Attackers often target domains using such selectors because they suggest that the domain is relying on default configurations, which could be less secure and easier to exploit. This can increase the risk of DKIM key exposure or misuse.
Risk description
Using a common DKIM selector makes it easier for attackers to predict and exploit email authentication weaknesses. Attackers may attempt to find corresponding DKIM keys or improperly managed records associated with common selectors. If a common selector is coupled with a weak key length or poor key management practices, it significantly increases the likelihood of email spoofing and phishing attacks.
Recommendation
We recommend using unique, customized selectors for each DKIM key to make it more difficult for attackers to predict and target the domain's DKIM records. Regularly rotate selectors and associated keys to further strengthen the security of your domain's email authentication infrastructure.
Evidence
We found insecure DNS cookie usage on the following nameservers: ns1.vh.pl, ns2.vh.pl
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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.safeandsoundremovals.co.uk | TXT | Text record | "v=DMARC1;p=quarantine;sp=none;adkim=r;aspf=r;pct=100;fo=0;rf=afrf;ri=86400;rua=mailto:dmarc@safeandsoundremovals.co.uk;ruf=mailto:dmarc@safeandsoundremovals.co.uk" |
Vulnerability description
We found that the DMARC record for the domain is configured with sp=none, meaning that no policy is enforced for subdomains. This allows subdomains to send emails without being subject to DMARC checks, making it easier for attackers to spoof emails from these subdomains. Subdomains are often overlooked in email security, and attackers can exploit this misconfiguration to launch phishing or spoofing attacks from seemingly legitimate subdomains of a protected domain.
Risk description
When the DMARC record is configured with sp=none, subdomains are not subject to DMARC enforcement, allowing attackers to spoof emails from subdomains without being blocked. This creates a significant risk of phishing and impersonation attacks, where malicious emails appear to originate from trusted subdomains. These spoofed emails can be used to deceive users or damage the organization's reputation, undermining the security benefits of DMARC for the primary domain.
Recommendation
To mitigate the risk, we recommend that the subdomain policy should be updated to sp=reject to ensure that any email failing DMARC checks from subdomains is automatically rejected. This will help prevent unauthorized emails from being sent from subdomains, reducing the risk of spoofing and phishing. Additionally, it's important to regularly monitor DMARC reports to track email activity from subdomains and adjust policies as needed to maintain consistent security across the entire domain.
Evidence
| Software / Version | Category |
|---|---|
| Nginx | Web servers, Reverse proxies |
| OpenResty 1.27.1.1 | Web servers |
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 |
|---|---|---|---|
| safeandsoundremovals.co.uk | A | IPv4 address | 83.168.99.244 |
| safeandsoundremovals.co.uk | NS | Name server | ns1.vh.pl |
| safeandsoundremovals.co.uk | NS | Name server | ns2.vh.pl |
| safeandsoundremovals.co.uk | MX | Mail server | 0 mail.safeandsoundremovals.co.uk |
| safeandsoundremovals.co.uk | SOA | Start of Authority | ns1.vh.pl. admin.vh.pl. 2026050105 3600 1800 1209600 86400 |
| safeandsoundremovals.co.uk | SPF | Sender Policy Framework | "v=spf1 include:spf.vh.net.pl -all" |
| _dmarc.safeandsoundremovals.co.uk | TXT | Text record | "v=DMARC1;p=quarantine;sp=none;adkim=r;aspf=r;pct=100;fo=0;rf=afrf;ri=86400;rua=mailto:dmarc@safeandsoundremovals.co.uk;ruf=mailto:dmarc@safeandsoundremovals.co.uk" |
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
| Software / Version | Category |
|---|---|
| Nginx | Web servers, Reverse proxies |
| OpenResty 1.27.1.1 | Web servers |
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 |
|---|---|---|---|
| safeandsoundremovals.co.uk | SPF | Sender Policy Framework | "v=spf1 include:spf.vh.net.pl -all" |
Evidence
| Software / Version | Category |
|---|---|
| Nginx | Web servers, Reverse proxies |
| OpenResty 1.27.1.1 | Web servers |
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
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| default | rsa | 1422 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsXujVq8QjS4ZInx1f5aAnR+swAP9EGzOJ3v/cUizUps3hujTXelb8rrUhO3M7+jpQpQMofX0OMPGIEpi61UO9i0hLvFi7MLRnZjuVPcl19RjSbDn3KKe7EtAVfP4nmmcjgu0f4j+UrmyaTRC73MJy443zHwxdQPqujNTDIfqKRuRiwRn877zeP+SktllPVA97" "h3DgPBzxne5wGHI4VEsgLdtw7+0kMvxUGhmLQUxRlTbCKGOm+XCF43ztueUXFYPsoEU/y7d6GSsZH1u7fXp80N8AsbuCVMJwXTIM76k2tJggok2iVfyo8bzFO5KpRwHZ1Y75scAvKMYDOmyDvFbXwIDAQAB;" |
Evidence
| Operating System | Accuracy |
|---|---|
| Linux 2.6.32 | 95% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| Nginx | Web servers, Reverse proxies |
| OpenResty 1.27.1.1 | Web servers |
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.