Vulnerability Scan Result
| Title: | Jay Santana Discography - Download Albums in Hi-Res - Qobuz |
| Description: | Listen to Jay Santana in unlimited streaming on Qobuz and buy the albums in Hi-Res 24-Bit for an unequalled sound quality. Subscription from $10.83/month |
| ip_address | 2.20.142.10 |
| country | DE  |
| network_name | Akamai International B.V |
| asn | AS20940 |
| ip_address | 2.20.143.107 |
| country | DE |
| network_name | Akamai International B.V |
| asn | AS20940 |
80/tcp | http | AkamaiGHost - |
443/tcp | https | - - |
| Software / Version | Category |
|---|---|
| Microsoft Advertising | Advertising |
| Akamai | CDN |
| Microsoft Clarity | Analytics |
| Bootstrap 93c41c80 | UI frameworks |
| Google Analytics | Analytics |
| HTTP/3 | Miscellaneous |
| jQuery 3.7.1 | JavaScript libraries |
| AOS | JavaScript libraries |
| Moment.js 2.30.1 | JavaScript libraries |
| New Relic | RUM |
| Open Graph | Miscellaneous |
| Unbounce | Editors, Page builders |
| AddToAny | Widgets |
| Algolia | Search engines |
| Google Tag Manager | Tag managers |
| OneTrust | Cookie compliance |
| Varnish | Caching |
Web Application Vulnerabilities
Evidence
Vulnerability description
We have noticed that the target application has overly permissive settings in its client access policy files. The crossdomain.xml file controls the access of externally hosted Flash scripts to this website, while clientaccesspolicy.xml specifies other sites that can read content from this website - which is normally denied by the Same Origin Policy. This vulnerability arises from configurations that grant excessive permissions to clients.
Risk description
In `crossdomain.xml`, the external websites which are permitted to read content from this website via Flash are specified in the XML tag `<allow-access-from>`. If the value of this tag is too permissive (ex. wildcard), it means that any Flash script from an external website could access content from this website, including confidential information of users. If the allowed domains are too permissive (ex. wildcard) in `clientaccesspolicy.xml`, then any external website will be able to read content (including sensitive information) from this website. Flash is not supported anymore and this poses a risk only if the user's clients use older browsers, making them vulnerable to their information being accessed by a malicious external Flash script.
Recommendation
We recommend to carefully review the content of the policy file and permit access only for legitimate domains.
Classification
| CWE | CWE-16 |
| 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
| Software / Version | Category |
|---|---|
| Microsoft Advertising | Advertising |
| Akamai | CDN |
| Microsoft Clarity | Analytics |
| Bootstrap 93c41c80 | UI frameworks |
| Google Analytics | Analytics |
| HTTP/3 | Miscellaneous |
| jQuery 3.7.1 | JavaScript libraries |
| AOS | JavaScript libraries |
| Moment.js 2.30.1 | JavaScript libraries |
| New Relic | RUM |
| Open Graph | Miscellaneous |
| Unbounce | Editors, Page builders |
| AddToAny | Widgets |
| Algolia | Search engines |
| Google Tag Manager | Tag managers |
| OneTrust | Cookie compliance |
| Varnish | Caching |
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://www.qobuz.com/us-en/interpreter/jay-santana/6693541 | 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://www.qobuz.com/us-en/interpreter/jay-santana/6693541 | Response headers include the HTTP Content-Security-Policy security header with the following security issues: |
Vulnerability description
We noticed that the Content-Security-Policy (CSP) header configured for the web application includes unsafe directives. The CSP header activates a protection mechanism implemented in web browsers which prevents exploitation of Cross-Site Scripting vulnerabilities (XSS) by restricting the sources from which content can be loaded or executed.
Risk description
For example, if the unsafe-inline directive is present in the CSP header, the execution of inline scripts and event handlers is allowed. This can be exploited by an attacker to execute arbitrary JavaScript code in the context of the vulnerable application.
Recommendation
Remove the unsafe values from the directives, adopt nonces or hashes for safer inclusion of inline scripts if they are needed, and explicitly define the sources from which scripts, styles, images or other resources can be loaded.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
Vulnerability description
Website is accessible.
Evidence
| URL | Method | Summary |
|---|---|---|
| https://www.qobuz.com/us-en/interpreter/jay-santana/6693541 | OPTIONS | We did a HTTP OPTIONS request. The server responded with a 405 status code and the header: `Allow: GET` 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 |
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
| CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
|---|---|---|---|---|---|
| CVE-2020-11023 | 6.9 | 0.27849 | 0.96262 | Yes | In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0. |
| CVE-2020-11022 | 6.9 | 0.30076 | 0.96466 | No | In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0. |
| CVE-2020-7656 | 6.1 | 0.0102 | 0.76628 | No | jquery prior to 1.9.0 allows Cross-site Scripting attacks via the load method. The load method fails to recognize and remove "<script>" HTML tags that contain a whitespace character, i.e: "</script >", which results in the enclosed script logic to be executed. |
| CVE-2019-11358 | 6.1 | 0.0548 | 0.89807 | No | jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype. |
| CVE-2015-9251 | 6.1 | 0.10091 | 0.92798 | No | jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses to be executed. |
Vulnerability description
Vulnerabilities found for jQuery 1.8.2
Risk description
These vulnerabilities expose the affected applications to the risk of unauthorized access to confidential data and possibly to denial of service attacks. An attacker could search for an appropriate exploit (or create one) for any of these vulnerabilities and use it to attack the system. Notes: - The vulnerabilities are identified based on the server's version.; - Only the first 5 vulnerabilities with the highest risk are shown for each port.; 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
We recommend you to upgrade the affected software to the latest version in order to eliminate the risks imposed by these vulnerabilities.
Evidence
We managed to detect that jQuery has reached the End-of-Life (EOL).
Version detected: 1.8.2 Latest version for the cycle: 1.12.4 This release cycle (1) doesn't have long-term-support (LTS). The cycle was released on 2006-08-31 and its latest release date was 2016-05-20.
Risk description
Using end-of-life (EOL) software poses significant security risks for organizations. EOL software no longer receives updates, including critical security patches. This creates a vulnerability landscape where known and potentially new security flaws remain unaddressed, making the software an attractive target for malicious actors. Attackers can exploit these vulnerabilities to gain unauthorized access, disrupt services, or steal sensitive data. Moreover, without updates, compatibility issues arise with newer technologies, leading to operational inefficiencies and increased potential for system failures. Additionally, regulatory and compliance risks accompany the use of EOL software. Many industries have strict data protection regulations that require up-to-date software to ensure the highest security standards. Non-compliance can result in hefty fines and legal consequences. Organizations also risk damaging their reputation if a breach occurs due to outdated software, eroding customer trust and potentially leading to a loss of business. Therefore, continuing to use EOL software undermines both security posture and business integrity, necessitating timely upgrades and proactive risk management strategies.
Recommendation
To mitigate the risks associated with end-of-life (EOL) software, it's crucial to take proactive steps. Start by identifying any EOL software currently in use within your organization. Once identified, prioritize upgrading or replacing these applications with supported versions that receive regular updates and security patches. This not only helps close security gaps but also ensures better compatibility with newer technologies, enhancing overall system efficiency and reliability.Additionally, develop a comprehensive software lifecycle management plan. This plan should include regular audits to identify upcoming EOL dates and a schedule for timely updates or replacements. Train your IT staff and users about the importance of keeping software up to date and the risks associated with using outdated versions. By maintaining a proactive approach to software management, you can significantly reduce security risks, ensure compliance with industry regulations, and protect your organization's reputation and customer trust.
Evidence
| Operating System | Accuracy |
|---|---|
| Linux 4.15 - 5.6 | 100% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| Unbounce | Editors, Page builders |
| Algolia | Search engines |
| Bootstrap 93c41c80 | UI frameworks |
| Varnish | Caching |
| GSAP | JavaScript frameworks |
| Cloudflare | CDN |
| OneTrust | Cookie compliance |
| Google Tag Manager | Tag managers |
| Google Analytics | Analytics |
| cdnjs | CDN |
| Akamai | CDN |
| HTTP/3 | Miscellaneous |
| jQuery 1.8.2 | JavaScript libraries |
| Google Hosted Libraries | CDN |
| SWFObject | Miscellaneous |
| Open Graph | 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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| www.qobuz.com | A | IPv4 address | 2.20.143.107 |
| www.qobuz.com | A | IPv4 address | 2.20.142.10 |
| www.qobuz.com | CNAME | Canonical name | www.qobuz.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.