Vulnerability Scan Result
IP address | 23.227.38.65 |
Country | CA |
AS number | AS13335 |
Net name | Cloudflare Inc |
80/tcp | http | Cloudflare http proxy |
443/tcp | https | Cloudflare http proxy |
8080/tcp | http | Cloudflare http proxy |
8443/tcp | https | Cloudflare http proxy |
Software / Version | Category |
---|---|
Google Ads | Advertising |
Boomerang | JavaScript libraries, RUM |
cdnjs | CDN |
jQuery CDN | CDN |
Facebook Pixel 2.9.179 | Analytics |
Font Awesome 4.7.0 | Font scripts |
LazySizes | JavaScript libraries, Performance |
jQuery Migrate 3.4.0 | JavaScript libraries |
core-js 3.32.2 | JavaScript libraries |
Google Analytics | Analytics |
HTTP/3 | Miscellaneous |
jQuery 3.6.0 | JavaScript libraries |
Open Graph | Miscellaneous |
PayPal | Payment processors |
Shopify | Ecommerce |
Google Ads Conversion Tracking | Analytics |
Priority Hints | Performance |
American Express | Payment processors |
Cloudflare | CDN |
Google Tag Manager | Tag managers |
Mastercard | Payment processors |
HSTS | Security |
Visa | Payment processors |
Cart Functionality | Ecommerce |
Web Application Vulnerabilities
Evidence
URL | Cookie Name | Evidence |
---|---|---|
https://q2turne.com/ | _shopify_s, _shopify_y, _tracking_consent, localization | The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: _shopify_s=ac36ad9c-b7a1-452c-bdc4-8c6a5ba93d07 Set-Cookie: _shopify_y=db6cb582-abd2-4d45-9cba-1e6fecb7772b Set-Cookie: _tracking_consent=%7B%22con%22%3A%7B%22CMP%22%3A%7B%22a%22%3A%22%22%2C%22m%22%3A%22%22%2C%22p%22%3A%22%22%2C%22s%22%3A%22%22%7D%7D%2C%22v%22%3A%222.1%22%2C%22region%22%3A%22GBENG%22%2C%22reg%22%3A%22%22%2C%22purposes%22%3A%7B%22a%22%3Atrue%2C%22p%22%3Atrue%2C%22m%22%3Atrue%2C%22t%22%3Atrue%7D%2C%22display_banner%22%3Afalse%2C%22sale_of_data_region%22%3Afalse%2C%22consent_id%22%3A%220E575A37-c95d-4BD1-b9b9-f1f4a404eed5%22%7D Set-Cookie: localization=BR |
Vulnerability description
We found that a cookie has been set without the <code>HttpOnly</code> 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.
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
URL | Cookie Name | Evidence |
---|---|---|
https://q2turne.com/ | _landing_page, _orig_referrer, _shopify_s, _shopify_y, _tracking_consent, localization | Set-Cookie: _landing_page=%2F Set-Cookie: _orig_referrer= Set-Cookie: _shopify_s=ac36ad9c-b7a1-452c-bdc4-8c6a5ba93d07 Set-Cookie: _shopify_y=db6cb582-abd2-4d45-9cba-1e6fecb7772b Set-Cookie: _tracking_consent=%7B%22con%22%3A%7B%22CMP%22%3A%7B%22a%22%3A%22%22%2C%22m%22%3A%22%22%2C%22p%22%3A%22%22%2C%22s%22%3A%22%22%7D%7D%2C%22v%22%3A%222.1%22%2C%22region%22%3A%22GBENG%22%2C%22reg%22%3A%22%22%2C%22purposes%22%3A%7B%22a%22%3Atrue%2C%22p%22%3Atrue%2C%22m%22%3Atrue%2C%22t%22%3Atrue%7D%2C%22display_banner%22%3Afalse%2C%22sale_of_data_region%22%3Afalse%2C%22consent_id%22%3A%220E575A37-c95d-4BD1-b9b9-f1f4a404eed5%22%7D Set-Cookie: localization=BR |
Vulnerability description
We found that a cookie has been set without the <code>Secure</code> 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.
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 | Evidence |
---|---|
https://q2turne.com/ | Response headers do not include the Referrer-Policy HTTP security header as well as the <meta> tag with name 'referrer' is not present in the response. |
Vulnerability description
We noticed that the target application's server responses lack the <code>Referrer-Policy</code> HTTP header, which controls how much referrer information the browser will send with each request originated from the current web application.
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
URL | Evidence |
---|---|
https://q2turne.com/ | Response headers include the HTTP Content-Security-Policy security header with the following security issues:`object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to 'none' or 'self'. script-src: script-src directive is missing.` |
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.
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 | A6 - Security Misconfiguration |
OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
Software / Version | Category |
---|---|
Google Ads | Advertising |
Boomerang | JavaScript libraries, RUM |
cdnjs | CDN |
jQuery CDN | CDN |
Facebook Pixel 2.9.179 | Analytics |
Font Awesome 4.7.0 | Font scripts |
LazySizes | JavaScript libraries, Performance |
jQuery Migrate 3.4.0 | JavaScript libraries |
core-js 3.32.2 | JavaScript libraries |
Google Analytics | Analytics |
HTTP/3 | Miscellaneous |
jQuery 3.6.0 | JavaScript libraries |
Open Graph | Miscellaneous |
PayPal | Payment processors |
Shopify | Ecommerce |
Google Ads Conversion Tracking | Analytics |
Priority Hints | Performance |
American Express | Payment processors |
Cloudflare | CDN |
Google Tag Manager | Tag managers |
Mastercard | Payment processors |
HSTS | Security |
Visa | Payment processors |
Cart Functionality | Ecommerce |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
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
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.
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).
Classification
OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
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.
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.
Classification
OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Infrastructure Vulnerabilities
Evidence
Domain Queried | DNS Record Type | Description | Value |
---|---|---|---|
q2turne.com | A | IPv4 address | 23.227.38.65 |
q2turne.com | NS | Name server | lee.ns.cloudflare.com |
q2turne.com | NS | Name server | lucy.ns.cloudflare.com |
q2turne.com | SOA | Start of Authority | lee.ns.cloudflare.com. dns.cloudflare.com. 2361487949 10000 2400 604800 1800 |
Recommendation
We recommend reviewing all DNS records associated with the domain and identifying and removing unused or obsolete records.
Vulnerability description
OS detection couldn't determine the operating system.
Recommendation
Vulnerability checks are skipped for ports that redirect to another port. We recommend scanning the redirected port directly.
Evidence
Software / Version | Category |
---|---|
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.
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 |
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.
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.