Vulnerability Scan Result
| Title: | הודעת אבטחה | Security notice | Aviso de seguridad - Did.Li |
| Description: | No description found |
| ip_address | 65.9.175.110 |
| country | US  |
| network_name | Amazon Inc |
| asn | AS16509 |
| ip_address | 65.9.175.114 |
| country | US |
| network_name | Amazon Inc |
| asn | AS16509 |
| ip_address | 65.9.175.39 |
| country | US |
| network_name | Amazon Inc |
| asn | AS16509 |
| ip_address | 65.9.175.60 |
| country | US |
| network_name | Amazon Inc |
| asn | AS16509 |
80/tcp | http | Amazon CloudFront httpd - |
443/tcp | https | CloudFront - |
| Software / Version | Category |
|---|---|
| Amazon Web Services | PaaS |
| AWS Certificate Manager | SSL/TLS certificate authorities |
| Amazon CloudFront | CDN |
| Amazon S3 | CDN |
| Elementor 3.33.1 | Page builders, WordPress plugins |
| Bootstrap 3.2.0 | UI frameworks |
| Elementor Header & Footer Builder | WordPress plugins |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| core-js 3.43.0 | JavaScript libraries |
| Google Analytics | Analytics |
| Google Font API | Font scripts |
| Isotope | JavaScript libraries |
| jQuery 3.7.1 | JavaScript libraries |
| jQuery UI 1.13.3 | JavaScript libraries |
| Lightbox | JavaScript libraries |
| Modernizr 2.6.2 | JavaScript libraries |
| MySQL | Databases |
| Nginx | Web servers, Reverse proxies |
| Open Graph | Miscellaneous |
| PhotoSwipe | Photo galleries, JavaScript libraries |
| PHP | Programming languages |
| Skrollr 0.6.29 | JavaScript libraries |
| Site Kit 1.166.0 | Analytics, WordPress plugins |
| WordPress 6.8.3 | CMS, Blogs |
| WP Rocket | Caching, WordPress plugins |
| AMP | JavaScript frameworks |
| Google AdSense | Advertising |
| Google Tag Manager | Tag managers |
| Master Slider 2.0.5 | Photo galleries |
| RSS | Miscellaneous |
| Yoast SEO 26.3 | SEO, WordPress plugins |
Web Application Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2024-6484 | 6.4 | 0.00049 | 0.15167 | 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. |
| CVE-2019-8331 | 6.1 | 0.02292 | 0.84186 | In Bootstrap before 3.4.1 and 4.3.x before 4.3.1, XSS is possible in the tooltip or popover data-template attribute. |
| CVE-2018-20677 | 6.1 | 0.11866 | 0.93442 | In Bootstrap before 3.4.0, XSS is possible in the affix configuration target property. |
| CVE-2018-20676 | 6.1 | 0.06144 | 0.90407 | In Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute. |
| CVE-2018-14042 | 6.1 | 0.01985 | 0.83024 | In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip. |
Vulnerability description
Outdated or vulnerable software components include versions of server-side software that are no longer supported or have known, publicly disclosed vulnerabilities. Using outdated software significantly increases the attack surface of a system and may allow unauthorized access, data leaks, or service disruptions. Vulnerabilities in these components are often well-documented and actively exploited by attackers. Without security patches or vendor support, any weaknesses remain unmitigated, exposing the application to risks. In some cases, even after patching, the reported version may remain unchanged, requiring manual verification.
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-1035 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://did.li/secure/ | 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 |
|---|---|
| Amazon Web Services | PaaS |
| AWS Certificate Manager | SSL/TLS certificate authorities |
| Amazon CloudFront | CDN |
| Amazon S3 | CDN |
| Elementor 3.33.1 | Page builders, WordPress plugins |
| Bootstrap 3.2.0 | UI frameworks |
| Elementor Header & Footer Builder | WordPress plugins |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| core-js 3.43.0 | JavaScript libraries |
| Google Analytics | Analytics |
| Google Font API | Font scripts |
| Isotope | JavaScript libraries |
| jQuery 3.7.1 | JavaScript libraries |
| jQuery UI 1.13.3 | JavaScript libraries |
| Lightbox | JavaScript libraries |
| Modernizr 2.6.2 | JavaScript libraries |
| MySQL | Databases |
| Nginx | Web servers, Reverse proxies |
| Open Graph | Miscellaneous |
| PhotoSwipe | Photo galleries, JavaScript libraries |
| PHP | Programming languages |
| Skrollr 0.6.29 | JavaScript libraries |
| Site Kit 1.166.0 | Analytics, WordPress plugins |
| WordPress 6.8.3 | CMS, Blogs |
| WP Rocket | Caching, WordPress plugins |
| AMP | JavaScript frameworks |
| Google AdSense | Advertising |
| Google Tag Manager | Tag managers |
| Master Slider 2.0.5 | Photo galleries |
| RSS | Miscellaneous |
| Yoast SEO 26.3 | SEO, WordPress plugins |
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
| URL | Evidence |
|---|---|
| https://did.li/secure/ | 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://did.li/secure/ | 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 | Method | Parameters | Evidence |
|---|---|---|---|
| https://did.li/secure/ | GET | Headers: User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 |
|
Vulnerability description
We noticed that the target application is serving mixed content. This occurs when initial HTML is loaded over a secure HTTPS connection, but other resources (such as images, videos, stylesheets, scripts) are loaded over an insecure HTTP connection. This is called mixed content because both HTTP and HTTPS content are being loaded to display the same page, and the initial request was secure over HTTPS.
Risk description
The risk is that the insecurely loaded resources (HTTP) on an otherwise secure page (HTTPS) can be intercepted or manipulated by attackers, potentially leading to eavesdropping or content tampering.
Recommendation
Ensure that all external resources the page references are loaded using HTTPS.
Classification
| CWE | CWE-311 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://did.li/secure/ | GET | Headers: User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 | Credit Card Number: 2644536267352236 |
Vulnerability description
We noticed that this application does not properly prevent a person's private, personal information from being accessed by actors who either (1) are not explicitly authorized to access the information or (2) do not have the implicit consent of the person about whom the information is collected. Sensitive data targeted usually consists of emails, credit card and social security numbers.
Risk description
The risk exists that sensitive personal information within the application could be accessed by unauthorized parties. This could lead to privacy violations, identity theft, or other forms of personal or corporate harm.
Recommendation
Compartmentalize the application to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
Evidence
| URL | Evidence |
|---|---|
| https://did.li/secure/ | 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
Vulnerability description
Website is accessible.
Evidence
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
We found insecure DNS cookie usage on the following nameservers: ns-113.awsdns-14.com, ns-1315.awsdns-36.org, ns-1639.awsdns-12.co.uk, ns-766.awsdns-31.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 |
|---|---|
| FreeBSD 11.0-RELEASE | 88% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| WordPress 6.8.3 | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| Google Sign-in | Authentication |
| Bootstrap | UI frameworks |
| Nginx | Web servers, Reverse proxies |
| Amazon Web Services | PaaS |
| WP Rocket | Caching, WordPress plugins |
| Elementor Header & Footer Builder | WordPress plugins |
| Elementor 3.33.1 | Page builders, WordPress plugins |
| Yoast SEO 26.3 | SEO, WordPress plugins |
| Site Kit 1.166.0 | Analytics, WordPress plugins |
| Lightbox | JavaScript libraries |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics | Analytics |
| Google AdSense | Advertising |
| Amazon S3 | CDN |
| Amazon CloudFront | CDN |
| AWS Certificate Manager | SSL/TLS certificate authorities |
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 |
|---|---|---|---|
| did.li | A | IPv4 address | 65.9.175.60 |
| did.li | A | IPv4 address | 65.9.175.114 |
| did.li | A | IPv4 address | 65.9.175.110 |
| did.li | A | IPv4 address | 65.9.175.39 |
| did.li | NS | Name server | ns-113.awsdns-14.com |
| did.li | NS | Name server | ns-1315.awsdns-36.org |
| did.li | NS | Name server | ns-1639.awsdns-12.co.uk |
| did.li | NS | Name server | ns-766.awsdns-31.net |
| did.li | MX | Mail server | 1 aspmx.l.google.com |
| did.li | MX | Mail server | 10 alt3.aspmx.l.google.com |
| did.li | MX | Mail server | 10 alt4.aspmx.l.google.com |
| did.li | MX | Mail server | 15 mk3xx5klvhzqeajt5thm36bcr5w7zu3ysi5tpkp3dzlj7bdqpykq.mx-verification.google.com |
| did.li | MX | Mail server | 5 alt1.aspmx.l.google.com |
| did.li | MX | Mail server | 5 alt2.aspmx.l.google.com |
| did.li | SOA | Start of Authority | ns-766.awsdns-31.net. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400 |
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.