Heartbleed OpenSSL bug
A vulnerability in the widely used OpenSSL cryptographic software library put an estimated two-thirds of the internet's encrypted websites at risk, forcing a mass, costly wave of credential resets and certificate replacements.
The damage was public. The root cause was preventable.
A vulnerability in the widely used OpenSSL cryptographic software library put an estimated two-thirds of the internet's encrypted websites at risk, forcing a mass, costly wave of credential resets and certificate replacements.
What the software actually got wrong
A missing bounds check in OpenSSL's 'heartbeat' extension let a malformed request cause a server to return up to 64 kilobytes of adjacent memory, potentially including private keys and passwords, and the bug had gone unnoticed in the open-source codebase for over two years before independent researchers found it.
A missing bounds check in OpenSSL's 'heartbeat' extension let...
A missing bounds check in OpenSSL's 'heartbeat' extension let a malformed request cause a server to return up to 64 kilobytes of adjacent memory, potentially including private keys and passwords
Requs AI Edge Case flags this exact pattern at the requirements and architecture stage — before a single line of code implementing it exists — so the assumption behind it gets challenged while it is still cheap to fix.
The bug had gone unnoticed in the open-source codebase...
the bug had gone unnoticed in the open-source codebase for over two years before independent researchers found it
Requs AI Software FMEA traces this failure mode back to the system-level hazard it feeds, tagging it against the Common Defect Enumeration so it surfaces in review instead of in the field.
Beyond code coverage and "shall" testing
Root causes like this one rarely show up in code coverage or requirements-compliance testing, because nobody wrote a requirement anticipating the specific edge case that broke. Requs AI Edge Case and Requs AI Software FMEA are built to surface exactly this class of overlooked failure mode — before the software is written.
Surfaces this before code exists
Identifies edge cases like this one at requirements and architecture time, using the Common Defect Enumeration to catalog failure patterns seen across hundreds of real-world software failures — including this one.
Connects the failure mode to the hazard
Traces this class of root cause directly to the system-level hazard it can produce, so a defect pattern like this one gets flagged during design review instead of after it ships.
Find the overlooked root causes before they ship.
Schedule a demonstration, or explore how Requs AI Edge Case and Software FMEA use the Common Defect Enumeration.