OWASP crAPI

Codeigniter .env file was discovered.

• http://localhost:8888/.env

A .env file was discovered containing sensitive information like database credentials and tokens. It should not be publicly accessible.

• http://localhost:8888/.env

A Laravel .env file was discovered, which stores sensitive information like database credentials and tokens. It should not be publicly accessible.

• http://localhost:8888/.env

• https://laravel.com/docs/master/configuration#environment-configuration
• https://stackoverflow.com/questions/38331397/how-to-protect-env-file-in-laravel

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:8888
• GET http://localhost:8888/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/

The response does not protect against 'ClickJacking' attacks. It should include either Content-Security-Policy with 'frame-ancestors' directive or X-Frame-Options.

• GET http://localhost:8888

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.

• https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Frame-Options

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:8888

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:8888

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

Cross-Origin-Resource-Policy header is an opt-in header designed to counter side-channels attacks like Spectre. Resource should be specifically set as shareable amongst different origins.

• GET http://localhost:8888
• GET http://localhost:8888/images/favicon.ico
• GET http://localhost:8888/images/logo192.png
• GET http://localhost:8888/manifest.json
• GET http://localhost:8888/robots.txt

Ensure that the application/web server sets the Cross-Origin-Resource-Policy header appropriately, and that it sets the Cross-Origin-Resource-Policy header to 'same-origin' for all web pages. 'same-site' is considered as less secured and should be avoided. If resources must be shared, set the header to 'cross-origin'. If possible, ensure that the end user uses a standards-compliant and modern web browser that supports the Cross-Origin-Resource-Policy header (https://caniuse.com/mdn-http_headers_cross-origin-resource-policy).

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

Permissions Policy Header is an added layer of security that helps to restrict from unauthorized access or usage of browser/client features by web resources. This policy ensures the user privacy by limiting or specifying the features of the browsers can be used by the web resources. Permissions Policy provides a set of standard HTTP headers that allow website owners to limit which features of browsers can be used by the page such as camera, microphone, location, full screen etc.

• GET http://localhost:8888
• GET http://localhost:8888/sitemap.xml
• GET http://localhost:8888/static/js/main.8c78208c.js

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

• https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Permissions-Policy
• https://developer.chrome.com/blog/feature-policy/
• https://scotthelme.co.uk/a-new-security-header-feature-policy/
• https://w3c.github.io/webappsec-feature-policy/

The web/application server is leaking version information via the "Server" HTTP response header. Access to such information may facilitate attackers identifying other vulnerabilities your web/application server is subject to.

• GET http://localhost:8888
• GET http://localhost:8888/images/logo192.png
• GET http://localhost:8888/manifest.json
• GET http://localhost:8888/robots.txt
• GET http://localhost:8888/sitemap.xml

Ensure that your web server, application server, load balancer, etc. is configured to suppress the "Server" header or provide generic details.

• https://httpd.apache.org/docs/current/mod/core.html#servertokens
• https://learn.microsoft.com/en-us/previous-versions/msp-n-p/ff648552(v=pandp.10)
• https://www.troyhunt.com/shhh-dont-let-your-response-headers/

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

• GET http://localhost:8888/static/js/main.8c78208c.js
• GET http://localhost:8888/static/js/main.8c78208c.js

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

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.

• GET http://localhost:8888
• GET http://localhost:8888/images/favicon.ico
• GET http://localhost:8888/images/logo192.png
• GET http://localhost:8888/manifest.json
• GET http://localhost:8888/robots.txt

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.

• https://learn.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/compatibility/gg622941(v=vs.85)
• https://owasp.org/www-community/Security_Headers

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:8888

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:8888
• GET http://localhost:8888/images/logo192.png
• GET http://localhost:8888/manifest.json
• GET http://localhost:8888/robots.txt
• GET http://localhost:8888/sitemap.xml

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