Vulnerability Scan Result
| Title: | No title found |
| Description: | No description found |
| ip_address | 216.137.44.68 |
| country | US  |
| network_name | Amazon Inc |
| asn | AS16509 |
| ip_address | 216.137.44.116 |
| country | US |
| network_name | Amazon Inc |
| asn | AS16509 |
| ip_address | 216.137.44.27 |
| country | US |
| network_name | Amazon Inc |
| asn | AS16509 |
| ip_address | 216.137.44.75 |
| country | US |
| network_name | Amazon Inc |
| asn | AS16509 |
80/tcp | http | Amazon CloudFront httpd - |
443/tcp | https | CloudFront - |
No technologies could be detected.
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://music.amazon.co.uk/podcasts/6039f33f-37bc-4ad6-becd-7aec5f123069/episodes/f65fe107-d1c3-4e76-90bf-9cd14f529c47/finance-history-single-currency | am-loader-experiment | Set-Cookie: .amazon.co.uk |
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 | Evidence |
|---|---|
| https://music.amazon.co.uk/podcasts/6039f33f-37bc-4ad6-becd-7aec5f123069/episodes/f65fe107-d1c3-4e76-90bf-9cd14f529c47/finance-history-single-currency | 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
| URL | Evidence |
|---|---|
| https://music.amazon.co.uk/podcasts/6039f33f-37bc-4ad6-becd-7aec5f123069/episodes/f65fe107-d1c3-4e76-90bf-9cd14f529c47/finance-history-single-currency | 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
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.
Evidence
| URL | Method | Summary |
|---|---|---|
| https://music.amazon.co.uk/podcasts/6039f33f-37bc-4ad6-becd-7aec5f123069/episodes/f65fe107-d1c3-4e76-90bf-9cd14f529c47/finance-history-single-currency?mc_cid=5c03fc584b&mc_eid=UNIQID | 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 |
|---|---|---|---|
| music.amazon.co.uk | A | IPv4 address | 216.137.44.27 |
| music.amazon.co.uk | A | IPv4 address | 216.137.44.75 |
| music.amazon.co.uk | A | IPv4 address | 216.137.44.68 |
| music.amazon.co.uk | A | IPv4 address | 216.137.44.116 |
| music.amazon.co.uk | NS | Name server | ns-1121.awsdns-12.org |
| music.amazon.co.uk | NS | Name server | ns-138.awsdns-17.com |
| music.amazon.co.uk | NS | Name server | ns-1572.awsdns-04.co.uk |
| music.amazon.co.uk | NS | Name server | ns-868.awsdns-44.net |
| music.amazon.co.uk | SOA | Start of Authority | ns-1572.awsdns-04.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400 |
| music.amazon.co.uk | AAAA | IPv6 address | 2600:9000:225c:9400:b:c5a0:c80:93a1 |
| music.amazon.co.uk | AAAA | IPv6 address | 2600:9000:225c:1800:b:c5a0:c80:93a1 |
| music.amazon.co.uk | AAAA | IPv6 address | 2600:9000:225c:200:b:c5a0:c80:93a1 |
| music.amazon.co.uk | AAAA | IPv6 address | 2600:9000:225c:e00:b:c5a0:c80:93a1 |
| music.amazon.co.uk | AAAA | IPv6 address | 2600:9000:225c:6e00:b:c5a0:c80:93a1 |
| music.amazon.co.uk | AAAA | IPv6 address | 2600:9000:225c:9000:b:c5a0:c80:93a1 |
| music.amazon.co.uk | AAAA | IPv6 address | 2600:9000:225c:400:b:c5a0:c80:93a1 |
| music.amazon.co.uk | AAAA | IPv6 address | 2600:9000:225c:7e00:b:c5a0:c80:93a1 |
| music.amazon.co.uk | CNAME | Canonical name | tp.b0000142f-frontier.amazon.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 |
|---|---|
| Node.js | Programming languages |
| Express | Web frameworks, Web servers |
| Amazon Web Services | PaaS |
| Amazon S3 | CDN |
| HSTS | Security |
| 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.