Vulnerability Scan Result
| Title: | Geolocation Check |
| Description: | No description found |
| IP address | 95.101.181.42 |
| Country | IT  |
| AS number | AS20940 |
| Net name | Akamai International B.V |
| IP address | 2.18.254.187 |
| Country | IT |
| AS number | AS20940 |
| Net name | Akamai International B.V |
80/tcp | http | AkamaiGHost - |
443/tcp | https | - - |
| Software / Version | Category |
|---|---|
| Google Ads | Advertising |
| Microsoft Advertising | Advertising |
| Akamai | CDN |
| Astute Solutions | CRM |
| Azure | PaaS |
| jQuery CDN | CDN |
| Adobe Experience Platform Identity Service | Customer data platform |
| Adobe Experience Platform Launch | Tag managers |
| Azure Front Door | Load balancers |
| web-vitals | JavaScript libraries, RUM |
| Axios | JavaScript libraries |
| Google Analytics | Analytics |
| HTTP/3 | Miscellaneous |
| Java | Programming languages |
| jQuery 3.5.1 | JavaScript libraries |
| Marko | Web frameworks, UI frameworks |
| Moment.js 2.24.0 | JavaScript libraries |
| Node.js | Programming languages |
| Google Ads Conversion Tracking | Analytics |
| Adobe Analytics | Analytics |
| Adobe Experience Manager | CMS |
| Adobe Target 2.10.2 | A/B Testing, Personalisation |
| DigiCert | SSL/TLS certificate authorities |
| Google Tag Manager | Tag managers |
| Invoca 4.39.7 | Marketing automation, Analytics |
| Qualtrics | Surveys |
| ServiceNow | Miscellaneous |
| YouTube | Video players |
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://www.aarpmedicaresupplement.com/privacypolicy.html | akamai_user_location | Set-Cookie: .aarpmedicaresupplement.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 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://www.aarpmedicaresupplement.com/privacypolicy.html | ApplicationGatewayAffinity, mnrdlm-state, userState, userStateName, mnrdlm-zipcode, akamai_user_location | Set-Cookie: ApplicationGatewayAffinity=46e945d8b19676e04ecc8c5bec837192 Set-Cookie: mnrdlm-state=(null) Set-Cookie: userState=MN Set-Cookie: userStateName=Minnesota Set-Cookie: mnrdlm-zipcode= Set-Cookie: akamai_user_location=country=GB,state= EN,city=,county=LONDON,zip= |
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 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://www.aarpmedicaresupplement.com/privacypolicy.html | ApplicationGatewayAffinityCORS, ApplicationGatewayAffinity, mnrdlm-state, userState, userStateName | The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: ApplicationGatewayAffinityCORS=46e945d8b19676e04ecc8c5bec837192 Set-Cookie: ApplicationGatewayAffinity=46e945d8b19676e04ecc8c5bec837192 Set-Cookie: mnrdlm-state=(null) Set-Cookie: userState=MN Set-Cookie: userStateName=Minnesota |
Vulnerability description
We found that a cookie has been set without the HttpOnly flag, which means it can be accessed by potentially malicious JavaScript code running inside the web page. The root cause for this usually revolves around misconfigurations in the code or server settings.
Risk description
The risk is that an attacker who injects malicious JavaScript code on the page (e.g. by using an XSS attack) can access the cookie and can send it to another site. In case of a session cookie, this could lead to session hijacking.
Recommendation
Ensure that the HttpOnly flag is set for all cookies.
Classification
| CWE | CWE-1004 |
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
| Risk Level | CVSS | CVE | Summary | Affected software |
|---|---|---|---|---|
| 5 | CVE-2022-24785 | Moment.js is a JavaScript date library for parsing, validating, manipulating, and formatting dates. A path traversal vulnerability impacts npm (server) users of Moment.js between versions 1.0.1 and 2.29.1, especially if a user-provided locale string is directly used to switch moment locale. This problem is patched in 2.29.2, and the patch can be applied to all affected versions. As a workaround, sanitize the user-provided locale name before passing it to Moment.js. | moment 2.24.0 | |
| 5 | CVE-2022-31129 | moment is a JavaScript date library for parsing, validating, manipulating, and formatting dates. Affected versions of moment were found to use an inefficient parsing algorithm. Specifically using string-to-date parsing in moment (more specifically rfc2822 parsing, which is tried by default) has quadratic (N^2) complexity on specific inputs. Users may notice a noticeable slowdown is observed with inputs above 10k characters. Users who pass user-provided strings without sanity length checks to moment constructor are vulnerable to (Re)DoS attacks. The problem is patched in 2.29.4, the patch can be applied to all affected versions with minimal tweaking. Users are advised to upgrade. Users unable to upgrade should consider limiting date lengths accepted from user input. | moment 2.24.0 |
Vulnerability description
We noticed known vulnerabilities in the target application based on the server responses. They are usually related to outdated systems and expose the affected applications to the risk of unauthorized access to confidential data and possibly denial of service attacks. Depending on the system distribution the affected software can be patched but displays the same version, requiring manual checking.
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.
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-1026 |
| OWASP Top 10 - 2017 | A9 - Using Components with Known Vulnerabilities |
| OWASP Top 10 - 2021 | A6 - Vulnerable and Outdated Components |
Evidence
| URL | Evidence |
|---|---|
| https://www.aarpmedicaresupplement.com/privacypolicy.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 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
| URL | Evidence |
|---|---|
| https://www.aarpmedicaresupplement.com/privacypolicy.html | 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 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
| URL | Evidence |
|---|---|
| https://www.aarpmedicaresupplement.com/privacypolicy.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 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
| Software / Version | Category |
|---|---|
| Google Ads | Advertising |
| Microsoft Advertising | Advertising |
| Akamai | CDN |
| Astute Solutions | CRM |
| Azure | PaaS |
| jQuery CDN | CDN |
| Adobe Experience Platform Identity Service | Customer data platform |
| Adobe Experience Platform Launch | Tag managers |
| Azure Front Door | Load balancers |
| web-vitals | JavaScript libraries, RUM |
| Axios | JavaScript libraries |
| Google Analytics | Analytics |
| HTTP/3 | Miscellaneous |
| Java | Programming languages |
| jQuery 3.5.1 | JavaScript libraries |
| Marko | Web frameworks, UI frameworks |
| Moment.js 2.24.0 | JavaScript libraries |
| Node.js | Programming languages |
| Google Ads Conversion Tracking | Analytics |
| Adobe Analytics | Analytics |
| Adobe Experience Manager | CMS |
| Adobe Target 2.10.2 | A/B Testing, Personalisation |
| DigiCert | SSL/TLS certificate authorities |
| Google Tag Manager | Tag managers |
| Invoca 4.39.7 | Marketing automation, Analytics |
| Qualtrics | Surveys |
| ServiceNow | Miscellaneous |
| YouTube | Video players |
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
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
Vulnerability description
Website is accessible.
Infrastructure Vulnerabilities
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| www.aarpmedicaresupplement.com | A | IPv4 address | 173.222.106.13 |
| www.aarpmedicaresupplement.com | A | IPv4 address | 173.222.106.55 |
| www.aarpmedicaresupplement.com | AAAA | IPv6 address | 2a02:26f0:df::212:fe7b |
| www.aarpmedicaresupplement.com | AAAA | IPv6 address | 2a02:26f0:df::210:16de |
| www.aarpmedicaresupplement.com | CNAME | Canonical name | www.aarpmedicaresupplement.com.edgekey.net |
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
| Operating System | Accuracy |
|---|---|
| Linux 4.15 - 5.6 | 100% |
Vulnerability description
OS Detection
Evidence
We managed to detect the redirect using the following Request / Response chain.
Recommendation
Vulnerability checks are skipped for ports that redirect to another port. We recommend scanning the redirected port directly.
Evidence
| Software / Version | Category |
|---|---|
| Adobe Experience Manager | CMS |
| Node.js | Programming languages |
| Java | Programming languages |
| Astute Solutions | CRM |
| Azure Front Door | Load balancers |
| Marko | Web frameworks, UI frameworks |
| YouTube | Video players |
| Azure | PaaS |
| DigiCert | SSL/TLS certificate authorities |
| Akamai | CDN |
| HTTP/3 | Miscellaneous |
| Google Ads | Advertising |
| Google Ads Conversion Tracking | Analytics |
| Qualtrics | Surveys |
| Microsoft Advertising | Advertising |
| jQuery CDN | CDN |
| jQuery 3.5.1 | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics | Analytics |
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.