Vulnerability findings for the public-facing infrastructure of facebook.com

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

• https://www.w3.org/TR/CSP/
• https://caniuse.com/#search=content+security+policy
• https://content-security-policy.com/
• https://github.com/HtmlUnit/htmlunit-csp
• https://web.dev/articles/csp#resource-options

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

• https://www.w3.org/TR/CSP/
• https://caniuse.com/#search=content+security+policy
• https://content-security-policy.com/
• https://github.com/HtmlUnit/htmlunit-csp
• https://web.dev/articles/csp#resource-options

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

• https://www.w3.org/TR/CSP/
• https://caniuse.com/#search=content+security+policy
• https://content-security-policy.com/
• https://github.com/HtmlUnit/htmlunit-csp
• https://web.dev/articles/csp#resource-options

Provide a valid integrity attribute to the tag.

• https://developer.mozilla.org/en-US/docs/Web/Security/Defenses/Subresource_Integrity

Ensure that the HttpOnly flag is set for all cookies.

• https://owasp.org/www-community/HttpOnly

Ensure that the SameSite attribute is set to either 'lax' or ideally 'strict' for all cookies.

• https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-cookie-same-site

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

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

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

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/
• https://www.smashingmagazine.com/2018/12/feature-policy/

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

Always scope cookies to a FQDN (Fully Qualified Domain Name).

• https://datatracker.ietf.org/doc/html/rfc6265#section-4.1
• https://owasp.org/www-project-web-security-testing-guide/v41/4-Web_Application_Security_Testing/06-Session_Management_Testing/02-Testing_for_Cookies_Attributes.html
• https://code.google.com/archive/p/browsersec/wikis/Part2.wiki

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

The content may be marked as storable by ensuring that the following conditions are satisfied:

The request method must be understood by the cache and defined as being cacheable ("GET", "HEAD", and "POST" are currently defined as cacheable)

The response status code must be understood by the cache (one of the 1XX, 2XX, 3XX, 4XX, or 5XX response classes are generally understood)

The "no-store" cache directive must not appear in the request or response header fields

For caching by "shared" caches such as "proxy" caches, the "private" response directive must not appear in the response

For caching by "shared" caches such as "proxy" caches, the "Authorization" header field must not appear in the request, unless the response explicitly allows it (using one of the "must-revalidate", "public", or "s-maxage" Cache-Control response directives)

In addition to the conditions above, at least one of the following conditions must also be satisfied by the response:

It must contain an "Expires" header field

It must contain a "max-age" response directive

For "shared" caches such as "proxy" caches, it must contain a "s-maxage" response directive

It must contain a "Cache Control Extension" that allows it to be cached

It must have a status code that is defined as cacheable by default (200, 203, 204, 206, 300, 301, 404, 405, 410, 414, 501).

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

This is an informational alert rather than a vulnerability and so there is nothing to fix.

• https://www.zaproxy.org/docs/desktop/addons/authentication-helper/session-mgmt-id/