Vulnerability Scan Result
| Title: | Phished |
| Description: | No description found |
| ip_address | 188.114.97.3 |
| country | - |
| network_name | Cloudflare, Inc. |
| asn | AS13335 |
| ip_address | 188.114.96.3 |
| country | - |
| network_name | Cloudflare, Inc. |
| asn | AS13335 |
80/tcp | http | Cloudflare http proxy - |
443/tcp | https | Cloudflare http proxy - |
2082/tcp | http | Cloudflare http proxy - |
2083/tcp | https | nginx - |
2086/tcp | http | Cloudflare http proxy - |
2087/tcp | https | nginx - |
8080/tcp | http | Cloudflare http proxy - |
8443/tcp | https | Cloudflare http proxy - |
| Software / Version | Category |
|---|---|
| Microsoft Clarity | Analytics |
| Google Cloud | IaaS |
| Google Cloud Trace | Performance |
| Bootstrap 4.5.3 | UI frameworks |
| Axios | JavaScript libraries |
| core-js 3.1.3 | JavaScript libraries |
| HTTP/3 | Miscellaneous |
| jQuery 3.5.1 | JavaScript libraries |
| PHP 8.4.18 | Programming languages |
| Popper | Miscellaneous |
| Webpack | Miscellaneous |
| Cloudflare | CDN |
| Lodash 4.17.20 | JavaScript libraries |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2021-23337 | 7.2 | 0.00741 | 0.72517 | Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function. |
| CVE-2020-28500 | 5.3 | 0.00245 | 0.47447 | Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions. |
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 | Cookie Name | Evidence |
|---|---|---|
| https://onlinemailing.be/nl/uitloggen/ | simulations_session, P_SEC_V | Set-Cookie: simulations_session=eyJpdiI6ImV6cjBDY1B3eEo1a0FWRC8xQ3lGaFE9PSIsInZhbHVlIjoiTTR5SVZQN3MrWUZKZnlUUmZEL25PMFg0aWExcUtJR3dNWHZKNW1WQ2RhM3h4MjJoNUtuek9meUJObzYyc3h3czZyUTNDdXB1emhFeUN1TmxVU0IvWmNFZmRhaWxNWVJsQ1N3YnVidjhxREorLytXN25sbGRaYnFhQ05uWm12SnkiLCJtYWMiOiIyNDZkMTE5YzY5YTk3ZTA0ZmExM2JiODExNDNjOTEyZDNiMTU1MmNkMDU2YzkzMDFjOGUzYzNlMDljNDhmZTE2IiwidGFnIjoiIn0%3D Set-Cookie: P_SEC_V=eyJpdiI6IlJnTWMySkdYWXVEMTA3WW4xSXFWK3c9PSIsInZhbHVlIjoiNWthR3Y5MkMzVm4yQ1lrcy9HanhBZGYzYnNtV2h3eFVjd2RWMlFEZXlabkRQcnAxRVdFYjFrMHkwUXNXMHZQamg4d0NnOHNqeC9pKzFiQzdPVmZRMm5Ld1AzSXBSc0VPL2VTMWxzMVE0SDg9IiwibWFjIjoiZTk3ZmRmMWRhYWUxMDJkNGYzOTVmYWQ2NjJmZDEwNDI5ZGI2MjlmM2RmZGIxNDA1YjFjNzRhNWUzN2UyZWZmYSIsInRhZyI6IiJ9 |
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://onlinemailing.be/nl/uitloggen/ | 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://onlinemailing.be/nl/uitloggen/ | GET | Query: sid=W4fcKhuaL4BboPXazf1XPn6X89bnRufxx9Q9 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 | Different hostname found for a source file |
Vulnerability description
We have noticed that the target application includes scripts from external domains. This may be problematic as such scripts have the same level of access as the application's own scripts, which means they can interact with application data and perform actions as the current user.
Risk description
The risk is that cross domain file inclusion can lead to a wide variety security breaches if the external scripts are malicious or become compromised.
Recommendation
You do not have any control over what is in that code. Ensure files on the site are loaded from only trusted sources.
Classification
| CWE | CWE-829 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
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
| URL | Method | Vulnerable Parameter | Evidence |
|---|---|---|---|
| https://onlinemailing.be/nl/uitloggen/ | GET | sid (Query Parameter) | Possible session token |
Vulnerability description
We found a possible session token exposed in an URL.
Risk description
The risk is that exposed session tokens can help an attacker hijack an existing user session. Placing sensible information within URLs increases the chances of it being leaked, as URLs might be logged in unexpected locations, or may be disclosed via the Referer header.
Recommendation
Session tokens should only be transmitted in HTTP cookies, POST submitted hidden form fields, or specialized auth headers.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://onlinemailing.be/nl/uitloggen/ | 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://onlinemailing.be/nl/uitloggen/ | 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 |
|---|---|
| Microsoft Clarity | Analytics |
| Google Cloud | IaaS |
| Google Cloud Trace | Performance |
| Bootstrap 4.5.3 | UI frameworks |
| Axios | JavaScript libraries |
| core-js 3.1.3 | JavaScript libraries |
| HTTP/3 | Miscellaneous |
| jQuery 3.5.1 | JavaScript libraries |
| PHP 8.4.18 | Programming languages |
| Popper | Miscellaneous |
| Webpack | Miscellaneous |
| Cloudflare | CDN |
| Lodash 4.17.20 | JavaScript libraries |
| 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
| URL | Method | Summary |
|---|---|---|
| https://onlinemailing.be/nl/uitloggen/?sid=W4fcKhuaL4BboPXazf1XPn6X89bnRufxx9Q9 | OPTIONS | We did a HTTP OPTIONS request. The server responded with a 200 status code and the header: `Allow: GET,HEAD` 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 | |
| OWASP Top 10 - 2021 |
Infrastructure Vulnerabilities
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.onlinemailing.be | TXT | Text record | "v=DMARC1; p=reject; rua=mailto:dmarc@phished.io; ruf=mailto:dmarc@phished.io; fo=1; pct=100" |
Vulnerability description
We found that the DMARC record for the domain is not configured with sp policy, meaning that no policy is enforced for subdomains. When a DMARC record does not include a subdomain policy (sp directive), subdomains are not explicitly covered by the main domain's DMARC policy. This means that emails sent from subdomains (e.g., sub.example.com) may not be subject to the same DMARC enforcement as the main domain (example.com). As a result, attackers could potentially spoof emails from subdomains without being blocked or flagged, even if the main domain has a strict DMARC policy.
Risk description
Without a subdomain policy (sp directive) in the DMARC record, subdomains are not protected by the same DMARC enforcement as the main domain, leaving them vulnerable to spoofing attacks. This inconsistency can be exploited by attackers to send phishing emails from subdomains, undermining the organization’s overall email security.
Recommendation
To mitigate the risk, we recommend configuring the DMARC record with a subdomain policy by adding the sp=reject or sp=quarantine directive. This will extend DMARC enforcement to all subdomains, preventing spoofing attempts and maintaining consistent security across both the main domain and its subdomains.
Evidence
We found insecure DNS cookie usage on the following nameservers: david.ns.cloudflare.com, melissa.ns.cloudflare.com
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
We checked 2056 selectors but found no DKIM records.
Vulnerability description
We found that no DKIM record was configured. When a DKIM (DomainKeys Identified Mail) record is not present for a domain, it means that outgoing emails from that domain are not cryptographically signed. DKIM is a critical component of email authentication, allowing recipients to verify that an email was genuinely sent from an authorized server and that the message has not been altered in transit. The absence of a DKIM record leaves the domain vulnerable to email spoofing and phishing attacks, as attackers can send fraudulent emails that appear to originate from the domain without any cryptographic verification.
Risk description
Without a DKIM record, recipients have no way of verifying the integrity or authenticity of emails sent from the domain. This increases the likelihood of phishing and spoofing attacks, where malicious actors impersonate the domain to send fraudulent emails. This can lead to significant security incidents, such as credential theft, financial fraud, or the distribution of malware. Additionally, many email providers use DKIM as part of their spam and reputation filters, meaning that emails from a domain without DKIM may be flagged as spam or rejected, impacting the deliverability and reputation of legitimate emails.
Recommendation
We recommend implementing DKIM for your domain to enhance email security and protect your brand from email-based attacks. Generate a DKIM key pair (public and private keys), publish the public key in the DNS under the appropriate selector, and configure your email servers to sign outgoing messages using the private key. Ensure that the DKIM key length is at least 1024 bits to prevent cryptographic attacks. Regularly monitor DKIM signatures to ensure the system is functioning correctly and update keys periodically to maintain security.
Evidence
| Operating System | Accuracy |
|---|---|
| FreeBSD 11.0-STABLE | 91% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
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 |
|---|---|---|---|
| onlinemailing.be | SPF | Sender Policy Framework | "v=spf1 ip4:143.55.236.227 ip4:143.55.236.228 ip4:143.55.236.247 ip4:34.140.69.192 ip4:34.22.133.124 include:mailgun.org -all" |
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| onlinemailing.be | A | IPv4 address | 188.114.96.3 |
| onlinemailing.be | A | IPv4 address | 188.114.97.3 |
| onlinemailing.be | NS | Name server | david.ns.cloudflare.com |
| onlinemailing.be | NS | Name server | melissa.ns.cloudflare.com |
| onlinemailing.be | MX | Mail server | 10 mxa.eu.mailgun.org |
| onlinemailing.be | MX | Mail server | 10 mxb.eu.mailgun.org |
| onlinemailing.be | SOA | Start of Authority | david.ns.cloudflare.com. dns.cloudflare.com. 2396495000 10000 2400 604800 1800 |
| onlinemailing.be | AAAA | IPv6 address | 2a06:98c1:3120::3 |
| onlinemailing.be | AAAA | IPv6 address | 2a06:98c1:3121::3 |
| onlinemailing.be | TXT | Text record | "google-site-verification=hvSIXz3TWpT5-IysDkEFJc7m0RzkYosr5hmRr-2w-u4" |
| onlinemailing.be | SPF | Sender Policy Framework | "v=spf1 ip4:143.55.236.227 ip4:143.55.236.228 ip4:143.55.236.247 ip4:34.140.69.192 ip4:34.22.133.124 include:mailgun.org -all" |
| _dmarc.onlinemailing.be | TXT | Text record | "v=DMARC1; p=reject; rua=mailto:dmarc@phished.io; ruf=mailto:dmarc@phished.io; fo=1; pct=100" |
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 |
|---|---|
| Cloudflare | CDN |
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 |
|---|---|
| PHP 8.4.18 | Programming languages |
| Google Cloud | IaaS |
| HSTS | Security |
| Google Cloud Trace | Performance |
| Cloudflare | CDN |
| HTTP/3 | 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
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
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.