error-handling
Safeguard articles tagged "error-handling" — guides, analysis, and best practices for software supply chain and application security.
6 articles
Nobody Chose to Fail Open. The Catch Block Did.
A permission check that throws, times out, or returns something unexpected proceeds as though access were granted, because a broad catch block written to handle an operational problem silently became an authorization bypass.
A Bare 400 Is Not a Security Posture
Empty error bodies get written by people worried about leaking internals, which is a real concern answered by the wrong control. Be precise about the caller's input, opaque about the system's state.
Uncaught Exception Security Risks
An uncaught exception isn't just a crash: it caused the Equifax breach and Log4j outages. See how exception-handling bugs become real security incidents.
Uncaught Exceptions in JavaScript: Handling Them Without Hiding Bugs
A JavaScript uncaught exception is a thrown error that no catch block claims — and the worst response is a global handler that swallows it. Here is how to handle them in Node and the browser without hiding real bugs.
JavaScript Uncaught Exceptions: A Security Guide
A JavaScript uncaught exception is more than a crash — unhandled errors leak internal detail, break security flows midway, and hide attacks. Here is how to handle them safely.
Uncaught Exception in Java: A Security Guide
An uncaught exception in Java is more than a crash - it leaks stack traces, kills threads, and opens denial-of-service paths. Here is how to handle it safely.
Self-healing security runs on Safeguard.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.