Issue summary: When an application passes a stack to
PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails,
OpenSSL frees every entry in the stack, both the old ones and any new
ones, but leaves them in the stack.
Impact summary: An application that passes an existing stack to
PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may
use memory that was already freed. This can cause a crash or, in
principle, memory corruption. Malformed PEM data can make the read fail,
but only applications that pass an existing stack are affected, and
OpenSSL itself does not do this.
CWE: CWE-416: Use After Free
Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and
private keys from PEM data and adds them to a stack of X509_INFO
structures. If the application passes a stack that is not NULL, the
function adds the new entries to it and must leave the entries that are
already there unchanged.
If reading fails, the function frees every entry in the stack. This
includes the entries that were there before the call, and the entries
added by the call. It does not remove these entries from the stack, so
the stack keeps pointers to freed memory. The failure can happen at any
point, even before any entry was added. A PEM item with invalid content
is enough. This also happens if the stack was empty: entries added
before the failure are freed but stay in the stack.
An application that then reads or frees the stack will use memory that
was already freed. This can crash the application or, in principle,
corrupt memory.
Only applications that pass a stack that is not NULL are affected.
OpenSSL itself never does this. Its own callers, including the code that
TLS uses to load CA certificates, always pass NULL. When the stack is
NULL, the function frees only the entries that it created itself, which
is safe. We expect that very few applications pass an existing stack. An
attacker can make the read fail with malformed PEM data, but cannot make
an application pass an existing stack.
The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read()
and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and
1.0.2 have only the first two of these functions.
FIPS impact: no
The affected code is outside the FIPS module boundary.
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.7): severity, escalated by confirmed exploitation. This CVE's 7.7 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.1% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it