Skip to main content
No exploitation reportedFix available

CVE-2022-4203

No exploitation reported by the sources we read.

  • Published2023-02-24
  • Fixed in3.0.8
  • WeaknessCWE-125

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

A read buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer. The read buffer overrun might result in a crash which could lead to a denial of service attack. In theory it could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext) although we are not aware of any working exploit leading to memory contents disclosure as of the time of release of this advisory. In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects.

Timeline

dates in UTC
  1. 2023-02-2415:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2022-4203?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2022-4203?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
OpenSSL
BranchAffectedFixed in
3.0≥ 3.0.0, < 3.0.83.0.8

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • ICSA-25-065-01 CISA3 products fixed · 3 known affected

    Hitachi Energy PCU400

    PCU400 versions 6.5 K and below · PCU400 versions 9.4.1 and below · PCULogger versions 1.1.0 and below

  • ICSA-23-320-08 CISA71 known affected

    Siemens SCALANCE Family Products

    SCALANCE XB205-3 (SC, PN) (6GK5205-3BB00-2AB2) · SCALANCE XB205-3 (ST, E/IP) (6GK5205-3BB00-2TB2) · SCALANCE XB205-3 (ST, E/IP) (6GK5205-3BD00-2TB2) · +68 more

  • ICSA-23-229-01 CISA1 known affected

    ICONICS and Mitsubishi Electric Products

    ICONICS Suite including GENESIS64, Hyper Historian, AnalytiX, and MobileHMI: 10.97.2

Full record on NVD

Fix

  1. Update OpenSSL to 3.0.8
  2. Vendor fix CISA ICSA-25-065-01 · 1 productIf IEC62351-3 secure for IEC104/DNP3 is used, then update to version 6.6.0 or latest
  3. Vendor fix CISA ICSA-25-065-01 · 1 productIf IEC62351-3 secure for IEC104/DNP3 is used, then update to version 9.4.2 or latest
  4. Vendor fix CISA ICSA-23-320-08 · 71 productsUpdate to V4.5 or later version
  5. Mitigation from the vendor CISA ICSA-23-229-01 · 1 productVersion 10.97.2 Critical Fixes Rollup 2 and later is not vulnerable to these exploits. ICONICS recommends that users of its products take the following mitigation steps:
  6. Mitigation from the vendor CISA ICSA-23-229-01 · 1 productEnsure the 10.97.2 Critical Fixes Rollup release is applied to version 10.97.2 systems.
  7. Mitigation from the vendor CISA ICSA-23-229-01 · 1 productFor systems that do not contain the patch/fix:

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
Published
2023-02-24
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2022-4203?

A read buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer. The read buffer overrun might result in a crash which could lead to a denial of service attack. In theory it could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext) although we are not aware of any working exploit leading to memory contents disclosure as of the time of release of this advisory. In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects.

Is CVE-2022-4203 actively exploited?

Active exploitation of CVE-2022-4203 has not been confirmed. Its EPSS score was 1.4% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2022-4203?

CVE-2022-4203 has a CVSS v3 base score of 4.9 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database