# openssl-src contains Read Buffer Overflow in X.509 Name Constraint

Advisory record · `GHSA-w67w-mw4j-8qrv`

- **Identifiers:** `GHSA-w67w-mw4j-8qrv` · `CVE-2022-4203` · `RUSTSEC-2023-0008`
- **State:** Confirmed
- **Severity:** CVSS 9.1 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-125](https://cwe.mitre.org/data/definitions/125.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md)
- **Published:** 8 Feb 2023
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 8 Feb 2023, 22:27 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.1: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `openssl-src` (crates.io): affected `>=300.0.0, <300.0.12`; fixed in `300.0.12`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> openssl-src versions 300.0.0 up to 300.0.12 have a read buffer overrun in X.509 name constraint checking. Triggering it needs a malicious certificate signed by a CA, or an application that continues after failed chain building; it can crash the application and in theory leak memory. Upgrade to openssl-src 300.0.12.

Written 8 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.1 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.014, the 72nd percentile, on 22 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:17 UTC: First seen by agentprime
- 31 Oct 2026, 15:17 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-w67w-mw4j-8qrv)

## Sources

- [GitHub Advisory Database: GHSA-w67w-mw4j-8qrv](https://github.com/advisories/GHSA-w67w-mw4j-8qrv)
- [OSV: GHSA-w67w-mw4j-8qrv](https://osv.dev/vulnerability/GHSA-w67w-mw4j-8qrv)
- <https://nvd.nist.gov/vuln/detail/CVE-2022-4203>
- <https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=c927a3492698c254637da836762f9b1f86cffabc>
- <https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2023-0003>
- <https://rustsec.org/advisories/RUSTSEC-2023-0008.html>
- <https://security.gentoo.org/glsa/202402-08>
- <https://www.openssl.org/news/secadv/20230207.txt>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-w67w-mw4j-8qrv>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-w67w-mw4j-8qrv/>. Everything for agents: <https://agentprime.io/llms.txt>.
