LambdaTest-Mastering-Automated-Security-Testing-Java/ZAP_Scan_Report.html at main · AutomateThePlanet/LambdaTest-Mastering-Automated-Security-Testing-Java · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
<html><head><title>ZAP Scan Report</title></head><body><h1>ZAP Scan Report</h1><h2>Summary</h2><table border='1'><tr><th>Risk Level</th><th>Count</th></tr><tr><td>Low</td><td>111</td></tr><tr><td>Medium</td><td>48</td></tr><tr><td>Informational</td><td>30</td></tr></table><h2>Detailed Findings</h2><table border='1'><tr><th>Alert</th><th>Risk</th><th>URL</th><th>Description</th><th>Solution</th></tr><tr><td>Content Security Policy (CSP) Header Not Set</td><td>Medium</td><td>http://juice-shop.herokuapp.com/ftp</td><td>Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate certain types of attacks, including Cross Site Scripting (XSS) and data injection attacks. These attacks are used for everything from data theft to site defacement or distribution of malware. CSP provides a set of standard HTTP headers that allow website owners to declare approved sources of content that browsers should be allowed to load on that page — covered types are JavaScript, CSS, HTML frames, fonts, images and embeddable objects such as Java applets, ActiveX, audio and video files.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to set the Content-Security-Policy header.</td></tr><tr><td>Content Security Policy (CSP) Header Not Set</td><td>Medium</td><td>http://juice-shop.herokuapp.com/sitemap.xml</td><td>Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate certain types of attacks, including Cross Site Scripting (XSS) and data injection attacks. These attacks are used for everything from data theft to site defacement or distribution of malware. CSP provides a set of standard HTTP headers that allow website owners to declare approved sources of content that browsers should be allowed to load on that page — covered types are JavaScript, CSS, HTML frames, fonts, images and embeddable objects such as Java applets, ActiveX, audio and video files.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to set the Content-Security-Policy header.</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>http://juice-shop.herokuapp.com/robots.txt</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>http://juice-shop.herokuapp.com/assets/public/favicon_js.ico</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>http://juice-shop.herokuapp.com/polyfills.js</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>http://juice-shop.herokuapp.com/runtime.js</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Content Security Policy (CSP) Header Not Set</td><td>Medium</td><td>http://juice-shop.herokuapp.com</td><td>Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate certain types of attacks, including Cross Site Scripting (XSS) and data injection attacks. These attacks are used for everything from data theft to site defacement or distribution of malware. CSP provides a set of standard HTTP headers that allow website owners to declare approved sources of content that browsers should be allowed to load on that page — covered types are JavaScript, CSS, HTML frames, fonts, images and embeddable objects such as Java applets, ActiveX, audio and video files.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to set the Content-Security-Policy header.</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>http://juice-shop.herokuapp.com</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>http://juice-shop.herokuapp.com/sitemap.xml</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Cross-Domain JavaScript Source File Inclusion</td><td>Low</td><td>http://juice-shop.herokuapp.com</td><td>The page includes one or more script files from a third-party domain.</td><td>Ensure JavaScript source files are loaded from only trusted sources, and the sources can't be controlled by end users of the application.</td></tr><tr><td>Cross-Domain JavaScript Source File Inclusion</td><td>Low</td><td>http://juice-shop.herokuapp.com/sitemap.xml</td><td>The page includes one or more script files from a third-party domain.</td><td>Ensure JavaScript source files are loaded from only trusted sources, and the sources can't be controlled by end users of the application.</td></tr><tr><td>Cross-Domain JavaScript Source File Inclusion</td><td>Low</td><td>http://juice-shop.herokuapp.com</td><td>The page includes one or more script files from a third-party domain.</td><td>Ensure JavaScript source files are loaded from only trusted sources, and the sources can't be controlled by end users of the application.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>http://juice-shop.herokuapp.com/assets/public/favicon_js.ico</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>http://juice-shop.herokuapp.com/robots.txt</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Cross-Domain JavaScript Source File Inclusion</td><td>Low</td><td>http://juice-shop.herokuapp.com/sitemap.xml</td><td>The page includes one or more script files from a third-party domain.</td><td>Ensure JavaScript source files are loaded from only trusted sources, and the sources can't be controlled by end users of the application.</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>http://juice-shop.herokuapp.com/main.js</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>http://juice-shop.herokuapp.com/styles.css</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Modern Web Application</td><td>Informational</td><td>http://juice-shop.herokuapp.com/sitemap.xml</td><td>The application appears to be a modern web application. If you need to explore it automatically then the Ajax Spider may well be more effective than the standard one.</td><td>This is an informational alert and so no changes are required.</td></tr><tr><td>Modern Web Application</td><td>Informational</td><td>http://juice-shop.herokuapp.com</td><td>The application appears to be a modern web application. If you need to explore it automatically then the Ajax Spider may well be more effective than the standard one.</td><td>This is an informational alert and so no changes are required.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>http://juice-shop.herokuapp.com/runtime.js</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>http://juice-shop.herokuapp.com/polyfills.js</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>http://juice-shop.herokuapp.com/ftp</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>http://juice-shop.herokuapp.com/sitemap.xml</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>http://juice-shop.herokuapp.com</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Information Disclosure - Suspicious Comments</td><td>Informational</td><td>http://juice-shop.herokuapp.com/main.js</td><td>The response appears to contain suspicious comments which may help an attacker. Note: Matches made within script blocks or files are against the entire content not only comments.</td><td>Remove all comments that return information that may help an attacker and fix any underlying problems they refer to.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>http://juice-shop.herokuapp.com/main.js</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>http://juice-shop.herokuapp.com/main.js</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>http://juice-shop.herokuapp.com/styles.css</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>http://juice-shop.herokuapp.com/assets/public/favicon_js.ico</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>http://juice-shop.herokuapp.com/ftp</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>http://juice-shop.herokuapp.com/robots.txt</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>http://juice-shop.herokuapp.com/runtime.js</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>http://juice-shop.herokuapp.com</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>http://juice-shop.herokuapp.com/sitemap.xml</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>http://juice-shop.herokuapp.com/polyfills.js</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>http://juice-shop.herokuapp.com/vendor.js</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>http://juice-shop.herokuapp.com/main.js</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>http://juice-shop.herokuapp.com/styles.css</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Information Disclosure - Suspicious Comments</td><td>Informational</td><td>http://juice-shop.herokuapp.com/vendor.js</td><td>The response appears to contain suspicious comments which may help an attacker. Note: Matches made within script blocks or files are against the entire content not only comments.</td><td>Remove all comments that return information that may help an attacker and fix any underlying problems they refer to.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>http://juice-shop.herokuapp.com/vendor.js</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>http://juice-shop.herokuapp.com/vendor.js</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>https://juice-shop.herokuapp.com/runtime.js</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Re-examine Cache-control Directives</td><td>Informational</td><td>https://juice-shop.herokuapp.com/</td><td>The cache-control header has not been set properly or is missing, allowing the browser and proxies to cache content. For static assets like css, js, or image files this might be intended, however, the resources should be reviewed to ensure that no sensitive content will be cached.</td><td>For secure content, ensure the cache-control HTTP header is set with "no-cache, no-store, must-revalidate". If an asset should be cached consider setting the directives "public, max-age, immutable".</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/runtime.js</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Content Security Policy (CSP) Header Not Set</td><td>Medium</td><td>https://juice-shop.herokuapp.com/</td><td>Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate certain types of attacks, including Cross Site Scripting (XSS) and data injection attacks. These attacks are used for everything from data theft to site defacement or distribution of malware. CSP provides a set of standard HTTP headers that allow website owners to declare approved sources of content that browsers should be allowed to load on that page — covered types are JavaScript, CSS, HTML frames, fonts, images and embeddable objects such as Java applets, ActiveX, audio and video files.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to set the Content-Security-Policy header.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/runtime.js</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>https://juice-shop.herokuapp.com/</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Cross-Domain JavaScript Source File Inclusion</td><td>Low</td><td>https://juice-shop.herokuapp.com/</td><td>The page includes one or more script files from a third-party domain.</td><td>Ensure JavaScript source files are loaded from only trusted sources, and the sources can't be controlled by end users of the application.</td></tr><tr><td>Cross-Domain JavaScript Source File Inclusion</td><td>Low</td><td>https://juice-shop.herokuapp.com/</td><td>The page includes one or more script files from a third-party domain.</td><td>Ensure JavaScript source files are loaded from only trusted sources, and the sources can't be controlled by end users of the application.</td></tr><tr><td>Modern Web Application</td><td>Informational</td><td>https://juice-shop.herokuapp.com/</td><td>The application appears to be a modern web application. If you need to explore it automatically then the Ajax Spider may well be more effective than the standard one.</td><td>This is an informational alert and so no changes are required.</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>https://cdnjs.cloudflare.com/ajax/libs/cookieconsent2/3.1.0/cookieconsent.min.css</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>https://juice-shop.herokuapp.com/polyfills.js</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Retrieved from Cache</td><td>Informational</td><td>https://cdnjs.cloudflare.com/ajax/libs/cookieconsent2/3.1.0/cookieconsent.min.css</td><td>The content was retrieved from a shared cache. If the response data is sensitive, personal or user-specific, this may result in sensitive information being leaked. In some cases, this may even result in a user gaining complete control of the session of another user, depending on the configuration of the caching components in use in their environment. This is primarily an issue where caching servers such as "proxy" caches are configured on the local network. This configuration is typically found in corporate or educational environments, for instance.</td><td>Validate that the response does not contain sensitive, personal or user-specific information. If it does, consider the use of the following HTTP response headers, to limit, or prevent the content being stored and retrieved from the cache by another user:
Cache-Control: no-cache, no-store, must-revalidate, private
Pragma: no-cache
Expires: 0
This configuration directs both HTTP 1.0 and HTTP 1.1 compliant caching servers to not store the response, and to not retrieve the response (without validation) from the cache, in response to a similar request.</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/polyfills.js</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/polyfills.js</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>https://cdnjs.cloudflare.com/ajax/libs/cookieconsent2/3.1.0/cookieconsent.min.js</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>https://cdnjs.cloudflare.com/ajax/libs/jquery/2.2.4/jquery.min.js</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Retrieved from Cache</td><td>Informational</td><td>https://cdnjs.cloudflare.com/ajax/libs/cookieconsent2/3.1.0/cookieconsent.min.js</td><td>The content was retrieved from a shared cache. If the response data is sensitive, personal or user-specific, this may result in sensitive information being leaked. In some cases, this may even result in a user gaining complete control of the session of another user, depending on the configuration of the caching components in use in their environment. This is primarily an issue where caching servers such as "proxy" caches are configured on the local network. This configuration is typically found in corporate or educational environments, for instance.</td><td>Validate that the response does not contain sensitive, personal or user-specific information. If it does, consider the use of the following HTTP response headers, to limit, or prevent the content being stored and retrieved from the cache by another user:
Cache-Control: no-cache, no-store, must-revalidate, private
Pragma: no-cache
Expires: 0
This configuration directs both HTTP 1.0 and HTTP 1.1 compliant caching servers to not store the response, and to not retrieve the response (without validation) from the cache, in response to a similar request.</td></tr><tr><td>Information Disclosure - Suspicious Comments</td><td>Informational</td><td>https://cdnjs.cloudflare.com/ajax/libs/jquery/2.2.4/jquery.min.js</td><td>The response appears to contain suspicious comments which may help an attacker. Note: Matches made within script blocks or files are against the entire content not only comments.</td><td>Remove all comments that return information that may help an attacker and fix any underlying problems they refer to.</td></tr><tr><td>Information Disclosure - Suspicious Comments</td><td>Informational</td><td>https://cdnjs.cloudflare.com/ajax/libs/jquery/2.2.4/jquery.min.js</td><td>The response appears to contain suspicious comments which may help an attacker. Note: Matches made within script blocks or files are against the entire content not only comments.</td><td>Remove all comments that return information that may help an attacker and fix any underlying problems they refer to.</td></tr><tr><td>Retrieved from Cache</td><td>Informational</td><td>https://cdnjs.cloudflare.com/ajax/libs/jquery/2.2.4/jquery.min.js</td><td>The content was retrieved from a shared cache. If the response data is sensitive, personal or user-specific, this may result in sensitive information being leaked. In some cases, this may even result in a user gaining complete control of the session of another user, depending on the configuration of the caching components in use in their environment. This is primarily an issue where caching servers such as "proxy" caches are configured on the local network. This configuration is typically found in corporate or educational environments, for instance.</td><td>Validate that the response does not contain sensitive, personal or user-specific information. If it does, consider the use of the following HTTP response headers, to limit, or prevent the content being stored and retrieved from the cache by another user:
Cache-Control: no-cache, no-store, must-revalidate, private
Pragma: no-cache
Expires: 0
This configuration directs both HTTP 1.0 and HTTP 1.1 compliant caching servers to not store the response, and to not retrieve the response (without validation) from the cache, in response to a similar request.</td></tr><tr><td>Vulnerable JS Library</td><td>Medium</td><td>https://cdnjs.cloudflare.com/ajax/libs/jquery/2.2.4/jquery.min.js</td><td>The identified library jquery, version 2.2.4 is vulnerable.</td><td>Please upgrade to the latest version of jquery.</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>https://juice-shop.herokuapp.com/main.js</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Information Disclosure - Suspicious Comments</td><td>Informational</td><td>https://juice-shop.herokuapp.com/main.js</td><td>The response appears to contain suspicious comments which may help an attacker. Note: Matches made within script blocks or files are against the entire content not only comments.</td><td>Remove all comments that return information that may help an attacker and fix any underlying problems they refer to.</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/main.js</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/main.js</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/main.js</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>https://juice-shop.herokuapp.com/styles.css</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/styles.css</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/styles.css</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>https://juice-shop.herokuapp.com/vendor.js</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Information Disclosure - Suspicious Comments</td><td>Informational</td><td>https://juice-shop.herokuapp.com/vendor.js</td><td>The response appears to contain suspicious comments which may help an attacker. Note: Matches made within script blocks or files are against the entire content not only comments.</td><td>Remove all comments that return information that may help an attacker and fix any underlying problems they refer to.</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/vendor.js</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/vendor.js</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Re-examine Cache-control Directives</td><td>Informational</td><td>https://juice-shop.herokuapp.com/assets/i18n/en.json</td><td>The cache-control header has not been set properly or is missing, allowing the browser and proxies to cache content. For static assets like css, js, or image files this might be intended, however, the resources should be reviewed to ensure that no sensitive content will be cached.</td><td>For secure content, ensure the cache-control HTTP header is set with "no-cache, no-store, must-revalidate". If an asset should be cached consider setting the directives "public, max-age, immutable".</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>https://juice-shop.herokuapp.com/assets/i18n/en.json</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Re-examine Cache-control Directives</td><td>Informational</td><td>https://juice-shop.herokuapp.com/rest/admin/application-configuration</td><td>The cache-control header has not been set properly or is missing, allowing the browser and proxies to cache content. For static assets like css, js, or image files this might be intended, however, the resources should be reviewed to ensure that no sensitive content will be cached.</td><td>For secure content, ensure the cache-control HTTP header is set with "no-cache, no-store, must-revalidate". If an asset should be cached consider setting the directives "public, max-age, immutable".</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>https://juice-shop.herokuapp.com/rest/admin/application-configuration</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Private IP Disclosure</td><td>Low</td><td>https://juice-shop.herokuapp.com/rest/admin/application-configuration</td><td>A private IP (such as 10.x.x.x, 172.x.x.x, 192.168.x.x) or an Amazon EC2 private hostname (for example, ip-10-0-56-78) has been found in the HTTP response body. This information might be helpful for further attacks targeting internal systems.</td><td>Remove the private IP address from the HTTP response body. For comments, use JSP/ASP/PHP comment instead of HTML/JavaScript comment which can be seen by client browsers.</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/rest/admin/application-configuration</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/rest/admin/application-configuration</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/rest/admin/application-configuration</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/rest/admin/application-configuration</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/assets/i18n/en.json</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/assets/i18n/en.json</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Re-examine Cache-control Directives</td><td>Informational</td><td>https://juice-shop.herokuapp.com/rest/admin/application-version</td><td>The cache-control header has not been set properly or is missing, allowing the browser and proxies to cache content. For static assets like css, js, or image files this might be intended, however, the resources should be reviewed to ensure that no sensitive content will be cached.</td><td>For secure content, ensure the cache-control HTTP header is set with "no-cache, no-store, must-revalidate". If an asset should be cached consider setting the directives "public, max-age, immutable".</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>https://juice-shop.herokuapp.com/rest/admin/application-version</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/rest/admin/application-version</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>https://juice-shop.herokuapp.com/MaterialIcons-Regular.woff2</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/rest/admin/application-version</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/MaterialIcons-Regular.woff2</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Re-examine Cache-control Directives</td><td>Informational</td><td>https://juice-shop.herokuapp.com/api/Challenges/?name=Score%20Board</td><td>The cache-control header has not been set properly or is missing, allowing the browser and proxies to cache content. For static assets like css, js, or image files this might be intended, however, the resources should be reviewed to ensure that no sensitive content will be cached.</td><td>For secure content, ensure the cache-control HTTP header is set with "no-cache, no-store, must-revalidate". If an asset should be cached consider setting the directives "public, max-age, immutable".</td></tr><tr><td>Re-examine Cache-control Directives</td><td>Informational</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaNwn</td><td>The cache-control header has not been set properly or is missing, allowing the browser and proxies to cache content. For static assets like css, js, or image files this might be intended, however, the resources should be reviewed to ensure that no sensitive content will be cached.</td><td>For secure content, ensure the cache-control HTTP header is set with "no-cache, no-store, must-revalidate". If an asset should be cached consider setting the directives "public, max-age, immutable".</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>https://juice-shop.herokuapp.com/api/Challenges/?name=Score%20Board</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/api/Challenges/?name=Score%20Board</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/api/Challenges/?name=Score%20Board</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaNwn</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaNwn</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>X-Content-Type-Options Header Missing</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaNwn</td><td>The Anti-MIME-Sniffing header X-Content-Type-Options was not set to 'nosniff'. This allows older versions of Internet Explorer and Chrome to perform MIME-sniffing on the response body, potentially causing the response body to be interpreted and displayed as a content type other than the declared content type. Current (early 2014) and legacy versions of Firefox will use the declared content type (if one is set), rather than performing MIME-sniffing.</td><td>Ensure that the application/web server sets the Content-Type header appropriately, and that it sets the X-Content-Type-Options header to 'nosniff' for all web pages.
If possible, ensure that the end user uses a standards-compliant and modern web browser that does not perform MIME-sniffing at all, or that can be directed by the web application/web server to not perform MIME-sniffing.</td></tr><tr><td>Re-examine Cache-control Directives</td><td>Informational</td><td>https://juice-shop.herokuapp.com/api/Quantitys/</td><td>The cache-control header has not been set properly or is missing, allowing the browser and proxies to cache content. For static assets like css, js, or image files this might be intended, however, the resources should be reviewed to ensure that no sensitive content will be cached.</td><td>For secure content, ensure the cache-control HTTP header is set with "no-cache, no-store, must-revalidate". If an asset should be cached consider setting the directives "public, max-age, immutable".</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>https://juice-shop.herokuapp.com/api/Quantitys/</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Re-examine Cache-control Directives</td><td>Informational</td><td>https://juice-shop.herokuapp.com/rest/languages</td><td>The cache-control header has not been set properly or is missing, allowing the browser and proxies to cache content. For static assets like css, js, or image files this might be intended, however, the resources should be reviewed to ensure that no sensitive content will be cached.</td><td>For secure content, ensure the cache-control HTTP header is set with "no-cache, no-store, must-revalidate". If an asset should be cached consider setting the directives "public, max-age, immutable".</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>https://juice-shop.herokuapp.com/rest/languages</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/api/Quantitys/</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/rest/languages</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/api/Quantitys/</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/rest/languages</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Missing Anti-clickjacking Header</td><td>Medium</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaO1Z&sid=GHmQ1HU8DBfHiwNkAAX0</td><td>The response does not protect against 'ClickJacking' attacks. It should include either Content-Security-Policy with 'frame-ancestors' directive or X-Frame-Options.</td><td>Modern Web browsers support the Content-Security-Policy and X-Frame-Options HTTP headers. Ensure one of them is set on all web pages returned by your site/app.
If you expect the page to be framed only by pages on your server (e.g. it's part of a FRAMESET) then you'll want to use SAMEORIGIN, otherwise if you never expect the page to be framed, you should use DENY. Alternatively consider implementing Content Security Policy's "frame-ancestors" directive.</td></tr><tr><td>Content Security Policy (CSP) Header Not Set</td><td>Medium</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaO1Z&sid=GHmQ1HU8DBfHiwNkAAX0</td><td>Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate certain types of attacks, including Cross Site Scripting (XSS) and data injection attacks. These attacks are used for everything from data theft to site defacement or distribution of malware. CSP provides a set of standard HTTP headers that allow website owners to declare approved sources of content that browsers should be allowed to load on that page — covered types are JavaScript, CSS, HTML frames, fonts, images and embeddable objects such as Java applets, ActiveX, audio and video files.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to set the Content-Security-Policy header.</td></tr><tr><td>Session ID in URL Rewrite</td><td>Medium</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaO1Z&sid=GHmQ1HU8DBfHiwNkAAX0</td><td>URL rewrite is used to track user session ID. The session ID may be disclosed via cross-site referer header. In addition, the session ID might be stored in browser history or server logs.</td><td>For secure content, put session ID in a cookie. To be even more secure consider using a combination of cookie and URL rewrite.</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaO1Z&sid=GHmQ1HU8DBfHiwNkAAX0</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaO1Z&sid=GHmQ1HU8DBfHiwNkAAX0</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>X-Content-Type-Options Header Missing</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaO1Z&sid=GHmQ1HU8DBfHiwNkAAX0</td><td>The Anti-MIME-Sniffing header X-Content-Type-Options was not set to 'nosniff'. This allows older versions of Internet Explorer and Chrome to perform MIME-sniffing on the response body, potentially causing the response body to be interpreted and displayed as a content type other than the declared content type. Current (early 2014) and legacy versions of Firefox will use the declared content type (if one is set), rather than performing MIME-sniffing.</td><td>Ensure that the application/web server sets the Content-Type header appropriately, and that it sets the X-Content-Type-Options header to 'nosniff' for all web pages.
If possible, ensure that the end user uses a standards-compliant and modern web browser that does not perform MIME-sniffing at all, or that can be directed by the web application/web server to not perform MIME-sniffing.</td></tr><tr><td>Re-examine Cache-control Directives</td><td>Informational</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaO1e&sid=GHmQ1HU8DBfHiwNkAAX0</td><td>The cache-control header has not been set properly or is missing, allowing the browser and proxies to cache content. For static assets like css, js, or image files this might be intended, however, the resources should be reviewed to ensure that no sensitive content will be cached.</td><td>For secure content, ensure the cache-control HTTP header is set with "no-cache, no-store, must-revalidate". If an asset should be cached consider setting the directives "public, max-age, immutable".</td></tr><tr><td>Session ID in URL Rewrite</td><td>Medium</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaO1e&sid=GHmQ1HU8DBfHiwNkAAX0</td><td>URL rewrite is used to track user session ID. The session ID may be disclosed via cross-site referer header. In addition, the session ID might be stored in browser history or server logs.</td><td>For secure content, put session ID in a cookie. To be even more secure consider using a combination of cookie and URL rewrite.</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaO1e&sid=GHmQ1HU8DBfHiwNkAAX0</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaO1e&sid=GHmQ1HU8DBfHiwNkAAX0</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>X-Content-Type-Options Header Missing</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaO1e&sid=GHmQ1HU8DBfHiwNkAAX0</td><td>The Anti-MIME-Sniffing header X-Content-Type-Options was not set to 'nosniff'. This allows older versions of Internet Explorer and Chrome to perform MIME-sniffing on the response body, potentially causing the response body to be interpreted and displayed as a content type other than the declared content type. Current (early 2014) and legacy versions of Firefox will use the declared content type (if one is set), rather than performing MIME-sniffing.</td><td>Ensure that the application/web server sets the Content-Type header appropriately, and that it sets the X-Content-Type-Options header to 'nosniff' for all web pages.
If possible, ensure that the end user uses a standards-compliant and modern web browser that does not perform MIME-sniffing at all, or that can be directed by the web application/web server to not perform MIME-sniffing.</td></tr><tr><td>Re-examine Cache-control Directives</td><td>Informational</td><td>https://content-autofill.googleapis.com/v1/pages/ChRDaHJvbWUvMTMxLjAuNjc3OC44NhIZCfaMrF9cuHRgEgUNFReaESHZlAR6K_fnvg==?alt=proto</td><td>The cache-control header has not been set properly or is missing, allowing the browser and proxies to cache content. For static assets like css, js, or image files this might be intended, however, the resources should be reviewed to ensure that no sensitive content will be cached.</td><td>For secure content, ensure the cache-control HTTP header is set with "no-cache, no-store, must-revalidate". If an asset should be cached consider setting the directives "public, max-age, immutable".</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://content-autofill.googleapis.com/v1/pages/ChRDaHJvbWUvMTMxLjAuNjc3OC44NhIZCfaMrF9cuHRgEgUNFReaESHZlAR6K_fnvg==?alt=proto</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Re-examine Cache-control Directives</td><td>Informational</td><td>https://juice-shop.herokuapp.com/rest/products/search?q=</td><td>The cache-control header has not been set properly or is missing, allowing the browser and proxies to cache content. For static assets like css, js, or image files this might be intended, however, the resources should be reviewed to ensure that no sensitive content will be cached.</td><td>For secure content, ensure the cache-control HTTP header is set with "no-cache, no-store, must-revalidate". If an asset should be cached consider setting the directives "public, max-age, immutable".</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>https://juice-shop.herokuapp.com/rest/products/search?q=</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/rest/products/search?q=</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/rest/products/search?q=</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/rest/products/search?q=</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/rest/products/search?q=</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Session ID in URL Rewrite</td><td>Medium</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=websocket&sid=GHmQ1HU8DBfHiwNkAAX0</td><td>URL rewrite is used to track user session ID. The session ID may be disclosed via cross-site referer header. In addition, the session ID might be stored in browser history or server logs.</td><td>For secure content, put session ID in a cookie. To be even more secure consider using a combination of cookie and URL rewrite.</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=websocket&sid=GHmQ1HU8DBfHiwNkAAX0</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/rest/admin/application-configuration</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Re-examine Cache-control Directives</td><td>Informational</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaO6q&sid=GHmQ1HU8DBfHiwNkAAX0</td><td>The cache-control header has not been set properly or is missing, allowing the browser and proxies to cache content. For static assets like css, js, or image files this might be intended, however, the resources should be reviewed to ensure that no sensitive content will be cached.</td><td>For secure content, ensure the cache-control HTTP header is set with "no-cache, no-store, must-revalidate". If an asset should be cached consider setting the directives "public, max-age, immutable".</td></tr><tr><td>Session ID in URL Rewrite</td><td>Medium</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaO6q&sid=GHmQ1HU8DBfHiwNkAAX0</td><td>URL rewrite is used to track user session ID. The session ID may be disclosed via cross-site referer header. In addition, the session ID might be stored in browser history or server logs.</td><td>For secure content, put session ID in a cookie. To be even more secure consider using a combination of cookie and URL rewrite.</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaO6q&sid=GHmQ1HU8DBfHiwNkAAX0</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaO6q&sid=GHmQ1HU8DBfHiwNkAAX0</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>X-Content-Type-Options Header Missing</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaO6q&sid=GHmQ1HU8DBfHiwNkAAX0</td><td>The Anti-MIME-Sniffing header X-Content-Type-Options was not set to 'nosniff'. This allows older versions of Internet Explorer and Chrome to perform MIME-sniffing on the response body, potentially causing the response body to be interpreted and displayed as a content type other than the declared content type. Current (early 2014) and legacy versions of Firefox will use the declared content type (if one is set), rather than performing MIME-sniffing.</td><td>Ensure that the application/web server sets the Content-Type header appropriately, and that it sets the X-Content-Type-Options header to 'nosniff' for all web pages.
If possible, ensure that the end user uses a standards-compliant and modern web browser that does not perform MIME-sniffing at all, or that can be directed by the web application/web server to not perform MIME-sniffing.</td></tr><tr><td>Missing Anti-clickjacking Header</td><td>Medium</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaO9Z&sid=GHmQ1HU8DBfHiwNkAAX0</td><td>The response does not protect against 'ClickJacking' attacks. It should include either Content-Security-Policy with 'frame-ancestors' directive or X-Frame-Options.</td><td>Modern Web browsers support the Content-Security-Policy and X-Frame-Options HTTP headers. Ensure one of them is set on all web pages returned by your site/app.
If you expect the page to be framed only by pages on your server (e.g. it's part of a FRAMESET) then you'll want to use SAMEORIGIN, otherwise if you never expect the page to be framed, you should use DENY. Alternatively consider implementing Content Security Policy's "frame-ancestors" directive.</td></tr><tr><td>Content Security Policy (CSP) Header Not Set</td><td>Medium</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaO9Z&sid=GHmQ1HU8DBfHiwNkAAX0</td><td>Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate certain types of attacks, including Cross Site Scripting (XSS) and data injection attacks. These attacks are used for everything from data theft to site defacement or distribution of malware. CSP provides a set of standard HTTP headers that allow website owners to declare approved sources of content that browsers should be allowed to load on that page — covered types are JavaScript, CSS, HTML frames, fonts, images and embeddable objects such as Java applets, ActiveX, audio and video files.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to set the Content-Security-Policy header.</td></tr><tr><td>Session ID in URL Rewrite</td><td>Medium</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaO9Z&sid=GHmQ1HU8DBfHiwNkAAX0</td><td>URL rewrite is used to track user session ID. The session ID may be disclosed via cross-site referer header. In addition, the session ID might be stored in browser history or server logs.</td><td>For secure content, put session ID in a cookie. To be even more secure consider using a combination of cookie and URL rewrite.</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaO9Z&sid=GHmQ1HU8DBfHiwNkAAX0</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaO9Z&sid=GHmQ1HU8DBfHiwNkAAX0</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>X-Content-Type-Options Header Missing</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaO9Z&sid=GHmQ1HU8DBfHiwNkAAX0</td><td>The Anti-MIME-Sniffing header X-Content-Type-Options was not set to 'nosniff'. This allows older versions of Internet Explorer and Chrome to perform MIME-sniffing on the response body, potentially causing the response body to be interpreted and displayed as a content type other than the declared content type. Current (early 2014) and legacy versions of Firefox will use the declared content type (if one is set), rather than performing MIME-sniffing.</td><td>Ensure that the application/web server sets the Content-Type header appropriately, and that it sets the X-Content-Type-Options header to 'nosniff' for all web pages.
If possible, ensure that the end user uses a standards-compliant and modern web browser that does not perform MIME-sniffing at all, or that can be directed by the web application/web server to not perform MIME-sniffing.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/runtime.js</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/polyfills.js</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/styles.css</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/vendor.js</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/main.js</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Re-examine Cache-control Directives</td><td>Informational</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaOM_</td><td>The cache-control header has not been set properly or is missing, allowing the browser and proxies to cache content. For static assets like css, js, or image files this might be intended, however, the resources should be reviewed to ensure that no sensitive content will be cached.</td><td>For secure content, ensure the cache-control HTTP header is set with "no-cache, no-store, must-revalidate". If an asset should be cached consider setting the directives "public, max-age, immutable".</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaOM_</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaOM_</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>X-Content-Type-Options Header Missing</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaOM_</td><td>The Anti-MIME-Sniffing header X-Content-Type-Options was not set to 'nosniff'. This allows older versions of Internet Explorer and Chrome to perform MIME-sniffing on the response body, potentially causing the response body to be interpreted and displayed as a content type other than the declared content type. Current (early 2014) and legacy versions of Firefox will use the declared content type (if one is set), rather than performing MIME-sniffing.</td><td>Ensure that the application/web server sets the Content-Type header appropriately, and that it sets the X-Content-Type-Options header to 'nosniff' for all web pages.
If possible, ensure that the end user uses a standards-compliant and modern web browser that does not perform MIME-sniffing at all, or that can be directed by the web application/web server to not perform MIME-sniffing.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/rest/admin/application-version</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/rest/admin/application-configuration</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/rest/languages</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/api/Quantitys/</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/assets/i18n/en.json</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Re-examine Cache-control Directives</td><td>Informational</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaOQ9&sid=dx6qYcjcLeH0xL4UAAX3</td><td>The cache-control header has not been set properly or is missing, allowing the browser and proxies to cache content. For static assets like css, js, or image files this might be intended, however, the resources should be reviewed to ensure that no sensitive content will be cached.</td><td>For secure content, ensure the cache-control HTTP header is set with "no-cache, no-store, must-revalidate". If an asset should be cached consider setting the directives "public, max-age, immutable".</td></tr><tr><td>Session ID in URL Rewrite</td><td>Medium</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaOQ9&sid=dx6qYcjcLeH0xL4UAAX3</td><td>URL rewrite is used to track user session ID. The session ID may be disclosed via cross-site referer header. In addition, the session ID might be stored in browser history or server logs.</td><td>For secure content, put session ID in a cookie. To be even more secure consider using a combination of cookie and URL rewrite.</td></tr><tr><td>Missing Anti-clickjacking Header</td><td>Medium</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaOQ4&sid=dx6qYcjcLeH0xL4UAAX3</td><td>The response does not protect against 'ClickJacking' attacks. It should include either Content-Security-Policy with 'frame-ancestors' directive or X-Frame-Options.</td><td>Modern Web browsers support the Content-Security-Policy and X-Frame-Options HTTP headers. Ensure one of them is set on all web pages returned by your site/app.
If you expect the page to be framed only by pages on your server (e.g. it's part of a FRAMESET) then you'll want to use SAMEORIGIN, otherwise if you never expect the page to be framed, you should use DENY. Alternatively consider implementing Content Security Policy's "frame-ancestors" directive.</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaOQ9&sid=dx6qYcjcLeH0xL4UAAX3</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaOQ9&sid=dx6qYcjcLeH0xL4UAAX3</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>X-Content-Type-Options Header Missing</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaOQ9&sid=dx6qYcjcLeH0xL4UAAX3</td><td>The Anti-MIME-Sniffing header X-Content-Type-Options was not set to 'nosniff'. This allows older versions of Internet Explorer and Chrome to perform MIME-sniffing on the response body, potentially causing the response body to be interpreted and displayed as a content type other than the declared content type. Current (early 2014) and legacy versions of Firefox will use the declared content type (if one is set), rather than performing MIME-sniffing.</td><td>Ensure that the application/web server sets the Content-Type header appropriately, and that it sets the X-Content-Type-Options header to 'nosniff' for all web pages.
If possible, ensure that the end user uses a standards-compliant and modern web browser that does not perform MIME-sniffing at all, or that can be directed by the web application/web server to not perform MIME-sniffing.</td></tr><tr><td>Content Security Policy (CSP) Header Not Set</td><td>Medium</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaOQ4&sid=dx6qYcjcLeH0xL4UAAX3</td><td>Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate certain types of attacks, including Cross Site Scripting (XSS) and data injection attacks. These attacks are used for everything from data theft to site defacement or distribution of malware. CSP provides a set of standard HTTP headers that allow website owners to declare approved sources of content that browsers should be allowed to load on that page — covered types are JavaScript, CSS, HTML frames, fonts, images and embeddable objects such as Java applets, ActiveX, audio and video files.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to set the Content-Security-Policy header.</td></tr><tr><td>Session ID in URL Rewrite</td><td>Medium</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaOQ4&sid=dx6qYcjcLeH0xL4UAAX3</td><td>URL rewrite is used to track user session ID. The session ID may be disclosed via cross-site referer header. In addition, the session ID might be stored in browser history or server logs.</td><td>For secure content, put session ID in a cookie. To be even more secure consider using a combination of cookie and URL rewrite.</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaOQ4&sid=dx6qYcjcLeH0xL4UAAX3</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaOQ4&sid=dx6qYcjcLeH0xL4UAAX3</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>X-Content-Type-Options Header Missing</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaOQ4&sid=dx6qYcjcLeH0xL4UAAX3</td><td>The Anti-MIME-Sniffing header X-Content-Type-Options was not set to 'nosniff'. This allows older versions of Internet Explorer and Chrome to perform MIME-sniffing on the response body, potentially causing the response body to be interpreted and displayed as a content type other than the declared content type. Current (early 2014) and legacy versions of Firefox will use the declared content type (if one is set), rather than performing MIME-sniffing.</td><td>Ensure that the application/web server sets the Content-Type header appropriately, and that it sets the X-Content-Type-Options header to 'nosniff' for all web pages.
If possible, ensure that the end user uses a standards-compliant and modern web browser that does not perform MIME-sniffing at all, or that can be directed by the web application/web server to not perform MIME-sniffing.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/rest/products/search?q=</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/api/Challenges/?name=Score%20Board</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Session ID in URL Rewrite</td><td>Medium</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=websocket&sid=dx6qYcjcLeH0xL4UAAX3</td><td>URL rewrite is used to track user session ID. The session ID may be disclosed via cross-site referer header. In addition, the session ID might be stored in browser history or server logs.</td><td>For secure content, put session ID in a cookie. To be even more secure consider using a combination of cookie and URL rewrite.</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=websocket&sid=dx6qYcjcLeH0xL4UAAX3</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Re-examine Cache-control Directives</td><td>Informational</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaOTl&sid=dx6qYcjcLeH0xL4UAAX3</td><td>The cache-control header has not been set properly or is missing, allowing the browser and proxies to cache content. For static assets like css, js, or image files this might be intended, however, the resources should be reviewed to ensure that no sensitive content will be cached.</td><td>For secure content, ensure the cache-control HTTP header is set with "no-cache, no-store, must-revalidate". If an asset should be cached consider setting the directives "public, max-age, immutable".</td></tr><tr><td>Session ID in URL Rewrite</td><td>Medium</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaOTl&sid=dx6qYcjcLeH0xL4UAAX3</td><td>URL rewrite is used to track user session ID. The session ID may be disclosed via cross-site referer header. In addition, the session ID might be stored in browser history or server logs.</td><td>For secure content, put session ID in a cookie. To be even more secure consider using a combination of cookie and URL rewrite.</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaOTl&sid=dx6qYcjcLeH0xL4UAAX3</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaOTl&sid=dx6qYcjcLeH0xL4UAAX3</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>X-Content-Type-Options Header Missing</td><td>Low</td><td>https://juice-shop.herokuapp.com/socket.io/?EIO=4&transport=polling&t=PESaOTl&sid=dx6qYcjcLeH0xL4UAAX3</td><td>The Anti-MIME-Sniffing header X-Content-Type-Options was not set to 'nosniff'. This allows older versions of Internet Explorer and Chrome to perform MIME-sniffing on the response body, potentially causing the response body to be interpreted and displayed as a content type other than the declared content type. Current (early 2014) and legacy versions of Firefox will use the declared content type (if one is set), rather than performing MIME-sniffing.</td><td>Ensure that the application/web server sets the Content-Type header appropriately, and that it sets the X-Content-Type-Options header to 'nosniff' for all web pages.
If possible, ensure that the end user uses a standards-compliant and modern web browser that does not perform MIME-sniffing at all, or that can be directed by the web application/web server to not perform MIME-sniffing.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/rest/admin/application-configuration</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Re-examine Cache-control Directives</td><td>Informational</td><td>https://juice-shop.herokuapp.com/rest/products/1/reviews</td><td>The cache-control header has not been set properly or is missing, allowing the browser and proxies to cache content. For static assets like css, js, or image files this might be intended, however, the resources should be reviewed to ensure that no sensitive content will be cached.</td><td>For secure content, ensure the cache-control HTTP header is set with "no-cache, no-store, must-revalidate". If an asset should be cached consider setting the directives "public, max-age, immutable".</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>https://juice-shop.herokuapp.com/rest/products/1/reviews</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Re-examine Cache-control Directives</td><td>Informational</td><td>https://juice-shop.herokuapp.com/rest/user/whoami</td><td>The cache-control header has not been set properly or is missing, allowing the browser and proxies to cache content. For static assets like css, js, or image files this might be intended, however, the resources should be reviewed to ensure that no sensitive content will be cached.</td><td>For secure content, ensure the cache-control HTTP header is set with "no-cache, no-store, must-revalidate". If an asset should be cached consider setting the directives "public, max-age, immutable".</td></tr><tr><td>Cross-Domain Misconfiguration</td><td>Medium</td><td>https://juice-shop.herokuapp.com/rest/user/whoami</td><td>Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.</td><td>Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/rest/products/1/reviews</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/rest/products/1/reviews</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://juice-shop.herokuapp.com/rest/user/whoami</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/rest/user/whoami</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr><tr><td>Re-examine Cache-control Directives</td><td>Informational</td><td>https://content-autofill.googleapis.com/v1/pages/ChRDaHJvbWUvMTMxLjAuNjc3OC44NhIgCaEBiZeIXdx-EgUNFReaERIFDVggm9gh-Y2Uh_jOA0s=?alt=proto</td><td>The cache-control header has not been set properly or is missing, allowing the browser and proxies to cache content. For static assets like css, js, or image files this might be intended, however, the resources should be reviewed to ensure that no sensitive content will be cached.</td><td>For secure content, ensure the cache-control HTTP header is set with "no-cache, no-store, must-revalidate". If an asset should be cached consider setting the directives "public, max-age, immutable".</td></tr><tr><td>Strict-Transport-Security Header Not Set</td><td>Low</td><td>https://content-autofill.googleapis.com/v1/pages/ChRDaHJvbWUvMTMxLjAuNjc3OC44NhIgCaEBiZeIXdx-EgUNFReaERIFDVggm9gh-Y2Uh_jOA0s=?alt=proto</td><td>HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.</td><td>Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.</td></tr><tr><td>Timestamp Disclosure - Unix</td><td>Low</td><td>https://juice-shop.herokuapp.com/rest/products/1/reviews</td><td>A timestamp was disclosed by the application/web server. - Unix</td><td>Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.</td></tr></table></body></html>