No classifications found.

Cross-site Referrer Leakage through usage of strict-origin in Referrer-Policy

Severity:
Information
Summary

Invicti detected that origin leakage is possible due to use of strict-origin in the Referrer-Policy implementation.

If a comma-separated referrer-policy is specified in the header, fallback policy is used only if the browser does not support the set referrer-policy, which may cause Cross-site Referrer Leakage.

Impact

Origin (Domain) information can be leaked through Referer header, if a request occurs to a site either has same or a higher protocol.

Remediation

If leakage of the origin is a problem for the site, see all available options by using links in External References and use a secure one.

Required Skills for Successful Exploitation
Actions To Take
Classifications
No items found.
Vulnerability Index

You can search and find all vulnerabilities

Select Vulnerability
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Related Vulnerabilities
No items found.

Featured resources

Blog

Strengthening enterprise application security: Invicti acquires Kondukto

Blog

Modern AppSec KPIs: Moving from scan counts to real risk reduction

Blog

Friends don’t let friends shift left: Shift smarter with DAST-first AppSec

Blog

Vibe talking: Dan Murphy on the promises, pitfalls, and insecurities of vibe coding

No items found.