OWASP Juice Shop

The identified library appears to be vulnerable.

• GET http://localhost:3005/vendor.js

Upgrade to the latest version of the affected library.

• https://owasp.org/Top10/2021/A06_2021-Vulnerable_and_Outdated_Components/

Prometheus metrics page was detected.

• http://localhost:3005/metrics

• https://github.com/prometheus/prometheus
• https://hackerone.com/reports/1026196

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.

• GET http://localhost:3005
• GET http://localhost:3005/ftp
• GET http://localhost:3005/ftp/encrypt.pyc
• GET http://localhost:3005/ftp/package.json.bak
• GET http://localhost:3005/sitemap.xml

Ensure that your web server, application server, load balancer, etc. is configured to set the Content-Security-Policy header.

• https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP
• https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html
• https://www.w3.org/TR/CSP/
• https://w3c.github.io/webappsec-csp/

Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.

• GET http://localhost:3005
• GET http://localhost:3005/robots.txt
• GET http://localhost:3005/runtime.js
• GET http://localhost:3005/sitemap.xml
• GET http://localhost:3005/styles.css

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.

• https://vulncat.fortify.com/en/detail?category=HTML5&subcategory=Overly%20Permissive%20CORS%20Policy

The page includes one or more script files from a third-party domain.

• GET http://localhost:3005
• GET http://localhost:3005
• GET http://localhost:3005/
• GET http://localhost:3005/sitemap.xml
• GET http://localhost:3005/sitemap.xml

Ensure JavaScript source files are loaded from only trusted sources, and the sources can't be controlled by end users of the application.

Cross-Origin-Embedder-Policy header is a response header that prevents a document from loading any cross-origin resources that don't explicitly grant the document permission (using CORP or CORS).

• GET http://localhost:3005
• GET http://localhost:3005/
• GET http://localhost:3005/ftp
• GET http://localhost:3005/juice-shop/build/routes/fileServer.js:59:18
• GET http://localhost:3005/sitemap.xml

Ensure that the application/web server sets the Cross-Origin-Embedder-Policy header appropriately, and that it sets the Cross-Origin-Embedder-Policy header to 'require-corp' for documents. If possible, ensure that the end user uses a standards-compliant and modern web browser that supports the Cross-Origin-Embedder-Policy header (https://caniuse.com/mdn-http_headers_cross-origin-embedder-policy).

• https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Cross-Origin-Embedder-Policy

Cross-Origin-Opener-Policy header is a response header that allows a site to control if others included documents share the same browsing context. Sharing the same browsing context with untrusted documents might lead to data leak.

• GET http://localhost:3005
• GET http://localhost:3005/
• GET http://localhost:3005/ftp
• GET http://localhost:3005/juice-shop/build/routes/fileServer.js:59:18
• GET http://localhost:3005/sitemap.xml

Ensure that the application/web server sets the Cross-Origin-Opener-Policy header appropriately, and that it sets the Cross-Origin-Opener-Policy header to 'same-origin' for documents. 'same-origin-allow-popups' is considered as less secured and should be avoided. If possible, ensure that the end user uses a standards-compliant and modern web browser that supports the Cross-Origin-Opener-Policy header (https://caniuse.com/mdn-http_headers_cross-origin-opener-policy).

• https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Cross-Origin-Opener-Policy

A dangerous JS function seems to be in use that would leave the site vulnerable.

• GET http://localhost:3005/main.js
• GET http://localhost:3005/vendor.js

See the references for security advice on the use of these functions.

• https://v17.angular.io/guide/security

The header has now been renamed to Permissions-Policy.

• GET http://localhost:3005
• GET http://localhost:3005/main.js
• GET http://localhost:3005/polyfills.js
• GET http://localhost:3005/runtime.js
• GET http://localhost:3005/sitemap.xml

Ensure that your web server, application server, load balancer, etc. is configured to set the Permissions-Policy header instead of the Feature-Policy header.

• https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Permissions-Policy
• https://scotthelme.co.uk/goodbye-feature-policy-and-hello-permissions-policy/

A timestamp was disclosed by the application/web server. - Unix

• GET http://localhost:3005
• GET http://localhost:3005
• GET http://localhost:3005
• GET http://localhost:3005/sitemap.xml
• GET http://localhost:3005/sitemap.xml

Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.

• https://cwe.mitre.org/data/definitions/200.html

Identifies the use of JavaScript addEventListener calls in the DOM.

• http://localhost:3005

• https://portswigger.net/web-security/dom-based/controlling-the-web-message-source

Detected the presence of the deprecated Feature-Policy HTTP response header. The Feature-Policy header has been deprecated and replaced by the Permissions-Policy header. While Feature-Policy is still supported in some browsers for backward compatibility, it is recommended to migrate to Permissions-Policy for future-proofing web applications.

• http://localhost:3005

• https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Feature-Policy
• https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy
• https://www.w3.org/TR/permissions-policy-1/
• https://github.com/w3c/webappsec-permissions-policy/blob/main/permissions-policy-explainer.md

FingerprintHub Technology Fingerprint tests run in nuclei.

• http://localhost:3005

• https://github.com/0x727/FingerprintHub

This template searches for missing HTTP security headers. The impact of these missing headers can vary.

• http://localhost:3005

This template searches for missing HTTP security headers. The impact of these missing headers can vary.

• http://localhost:3005

This template searches for missing HTTP security headers. The impact of these missing headers can vary.

• http://localhost:3005

This template searches for missing HTTP security headers. The impact of these missing headers can vary.

• http://localhost:3005

This template searches for missing HTTP security headers. The impact of these missing headers can vary.

• http://localhost:3005

This template searches for missing HTTP security headers. The impact of these missing headers can vary.

• http://localhost:3005

This template searches for missing HTTP security headers. The impact of these missing headers can vary.

• http://localhost:3005

This template searches for missing HTTP security headers. The impact of these missing headers can vary.

• http://localhost:3005

Checks if external script and stylesheet tags in the HTML response are missing the Subresource Integrity (SRI) attribute.

• http://localhost:3005/

• https://cheatsheetseries.owasp.org/cheatsheets/Third_Party_Javascript_Management_Cheat_Sheet.html#subresource-integrity
• https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity

• http://localhost:3005

Public Swagger API was detected.

• http://localhost:3005/api-docs/swagger.json

• https://swagger.io/

Websites that advertise jobs via HTTP headers

• http://localhost:3005

• https://webtechsurvey.com/response-header/x-recruiting

• http://localhost:3005/robots.txt

• http://localhost:3005/robots.txt

File similar to robots.txt but intended to be read by humans wishing to contact a website’s owner about security issues. Often defines a security policy and contact details.

• http://localhost:3005/.well-known/security.txt

• https://securitytxt.org/
• https://community.turgensec.com/security-txt-progress-in-ethical-security-research/

The application appears to be a modern web application. If you need to explore it automatically then the Client Spider may well be more effective than the standard one.

• GET http://localhost:3005
• GET http://localhost:3005/
• GET http://localhost:3005/juice-shop/build/routes/fileServer.js:59:18
• GET http://localhost:3005/juice-shop/node_modules/express/lib/router/layer.js:95:5
• GET http://localhost:3005/sitemap.xml

This is an informational alert and so no changes are required.

The response contents are storable by caching components such as proxy servers, and may be retrieved directly from the cache, rather than from the origin server by the caching servers, in response to similar requests from other users. 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 "shared" caching servers such as "proxy" caches are configured on the local network. This configuration is typically found in corporate or educational environments, for instance.

• GET http://localhost:3005/ftp
• GET http://localhost:3005/robots.txt

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.

• https://datatracker.ietf.org/doc/html/rfc7234
• https://datatracker.ietf.org/doc/html/rfc7231
• https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html

The response contents are storable by caching components such as proxy servers, but will not be retrieved directly from the cache, without validating the request upstream, in response to similar requests from other users.

• GET http://localhost:3005
• GET http://localhost:3005/assets/public/favicon_js.ico
• GET http://localhost:3005/runtime.js
• GET http://localhost:3005/sitemap.xml
• GET http://localhost:3005/styles.css

• https://datatracker.ietf.org/doc/html/rfc7234
• https://datatracker.ietf.org/doc/html/rfc7231
• https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html