CWE-293 Using the Referer Header for Authentication
The Referer header is set by the client, so it proves nothing. Learn why checking it as a login or authorization step fails and what to check instead.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
The Referer header is set by the client, so it proves nothing. Learn why checking it as a login or authorization step fails and what to check instead.
Treating a source IP as proof of identity lets attackers who can forge or reach that address walk in. Here is how the weakness works and what to use instead.
CWE-290 is authentication built on values an attacker can forge, like a source IP or a Host header. Learn why those checks fail and what to use instead.
Filters that only watch for forward slashes miss backslash sequences on Windows. How CWE-29 works and how to close the gap.
CWE-289 is checking access by name but missing the other names for the same resource. Encoded URLs and backslashes show how it works and how to fix it.
CWE-288 is a login that guards the front door while a side door stays open. See real examples, how to enumerate every path to a resource, and how to close them.
CWE-287 is software that does not prove a claimed identity. Learn how real products skipped login checks and what a sound authentication design looks like.
CWE-286 is mismanaging users so they land in the wrong permission group. See the observed CVEs and a short checklist for reviewing group assignment.
CWE-285 is a missing or wrong authorization check when someone accesses a resource. See real CVEs, a code example, test steps, and a central policy fix.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.