NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🦀
🦀 crates.io
Not in CISA KEV
HIGH severity

CVE-2022-4450 — openssl-src

HIGH

CVE-2022-4450 is a high-severity (CVSS 7.5) CWE-415 vulnerability in openssl-src. EPSS puts its 30-day exploitation probability at 28.6% (98th percentile). A fix is available for openssl-src — see the affected versions and patch details below.

Double free after calling PEM_read_bio_ex

Also known asGHSA-v5w6-wcm8-jm4qRUSTSEC-2023-0010
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-4450.

EPSS Exploitation Probability

via FIRST.org ↗
28.6%probability of exploitation in next 30 days
Moderate Risk0.00%
Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk
0.00%12.4%24.7%37.1%0.1%28.6%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
🦀openssl-src🦀openssl-src

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack.

The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected.

These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0.

The OpenSSL asn1parse command line application is also impacted by this issue.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.ioopenssl-srcall versions111.25.0cargo update -p openssl-src --precise 111.25.0
🦀crates.ioopenssl-src≥ 300.0.0&&< 300.0.12300.0.12cargo update -p openssl-src --precise 300.0.12

Affected Products

2 products · 4 configurations
Application
opensslopenssl
≥ 3.0.0 && < 3.0.8
range
Application
stormshield network securitystormshield
≥ 4.4.0 && < 4.6.3
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openssl-src, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update openssl-src to 111.25.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-4450 is resolved across your whole dependency graph.

  3. Workarounds

    Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

A double-free vulnerability was found in the OpenSSL library in the PEM_read_bio_ex() function and its wrappers. The flaw is triggered when the library parses a specially crafted PEM file constructed to have zero bytes of payload data. This edge case causes the function to return a failure code but also populate a…

ProductFixed inAdvisory
JBCS httpd 2.4.51.sp2opensslRHSA-2023:3355
JBoss Core Services for RHEL 8jbcs-httpd24-openssl-1:1.1.1k-14.el8jbcsRHSA-2023:3354
Red Hat Enterprise Linux 8edk2-0:20220126gitbb1bba3d77-4.el8RHSA-2023:2932
Red Hat Enterprise Linux 8openssl-1:1.1.1k-9.el8_7RHSA-2023:1405
Red Hat Enterprise Linux 8.6 Extended Update Supportopenssl-1:1.1.1k-9.el8_6RHSA-2023:3408
Red Hat Enterprise Linux 9openssl-1:3.0.1-47.el9_1RHSA-2023:0946
Red Hat Enterprise Linux 9edk2-0:20221207gitfff6d81270b5-9.el9_2RHSA-2023:2165
Red Hat Enterprise Linux 9.0 Extended Update Supportopenssl-1:3.0.1-46.el9_0RHSA-2023:1199

Frequently Asked Questions

The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the ca
O3 Security · Impact-Aware SCA

Is CVE-2022-4450 in your dependencies?

Find it across crates.io, including transitive dependencies.

CVE-2022-4450: openssl-src DoS — Fixed in 111.25.0