CWE-50 Multiple Leading Slash Path Equivalence: Causes and Fixes
A request starting with two slashes can read arbitrary files or skip authentication. CWE-50 explained, with a normalization fix.
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.
A request starting with two slashes can read arbitrary files or skip authentication. CWE-50 explained, with a normalization fix.
A J2EE app configured to send data in plaintext lets anyone on the network path read or change it. Here is how the weakness shows up and how to close it.
A Java class that holds secrets and does not deny serialization can be written to a byte stream by any other class. Learn the pattern and the two standard fixes.
A class that holds secrets but allows cloning can be copied without running its constructor. Here is how that bypasses checks and how to close it off in Java, C++ and C#.
Stack traces, paths and version banners help attackers plan. How system information leaks out of web apps and the logging and error handling that stops it.
Storing a caller's array in a private field keeps the caller's handle on it. Copy the array on the way in so the private field stays private.
A getter that hands back a reference to a private array or list lets callers change your internal state. Return copies or read only views instead.
Software that fetches and runs code without verifying it trusts the network and the host. Learn how signing and verification close the gap in updates and installers.
A public field that is not final can be rewritten by any code that reaches the class. Make critical fields final, or stop exposing them.
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.