CVE Tools

CVE-2025-9232

Out-of-bounds read in HTTP client no_proxy handling

No known exploitation. EPSS puts it in the 84th percentile. Fixed versions are out.

Check it yourself

OpenVAS · 33 checks

e.g. OID 1.3.6.1.4.1.25623.1.0.118835

Run the check

Published Updated Sources: CVE.org, NVD, BDU, CSAF

What to do

Find your product and version, then upgrade to the build on the right.

  • OpenSSLAffected: ≥ 3.5.0, < 3.5.4Upgrade to: 3.5.4Affected: ≥ 3.4.0, < 3.4.3Upgrade to: 3.4.3Affected: ≥ 3.3.3, < 3.3.5Upgrade to: 3.3.5Affected: ≥ 3.2.4, < 3.2.6Upgrade to: 3.2.6 + 1 more branchStated by: CVE record
  • Siemens Simatic Cn 4100 FirmwareAffected: < 5.0Upgrade to: 5.0Stated by: NVD
  • Siemens Sinec OsAffected: < 3.3Upgrade to: 3.3Stated by: NVD
  • Siemens Ruggedcom Rst2428p FirmwareAffected: < 4.0Upgrade to: 4.0Stated by: NVD
  • Siemens Sidis PrimeAffected: < 4.0.800Upgrade to: 4.0.800Stated by: NVD

Versions as the sources state them. 4 more products have version data. Full version matrix after sign-in

What it is

From the CVE record

Issue summary: An application using the OpenSSL HTTP client API functions may trigger an out-of-bounds read if the 'no_proxy' environment variable is set and the host portion of the authority component of the HTTP URL is an IPv6 address. Impact summary: An out-of-bounds read can trigger a crash which leads to Denial of Service for an application. The OpenSSL HTTP client API functions can be used directly by applications but they are also used by the OCSP client functions and CMP (Certificate Management Protocol) client implementation in OpenSSL. However the URLs used by these implementations are unlikely to be controlled by an attacker. In this vulnerable code the out of bounds read can only trigger a crash. Furthermore the vulnerability requires an attacker-controlled URL to be passed from an application to the OpenSSL function and the user has to have a 'no_proxy' environment variable set. For the aforementioned reasons the issue was assessed as Low severity. The vulnerable code was introduced in the following patch releases: 3.0.16, 3.1.8, 3.2.4, 3.3.3, 3.4.0 and 3.5.0. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the HTTP client implementation is outside the OpenSSL FIPS module boundary.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS84th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

2.4% chance of exploitation activity in the next 30 days, which ranks it in the 84th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

12 events over 405 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Patch availablerecord updated
  3. Patch availablerecord updated
  4. OpenVAS check added
  5. Patch availablerecord updated
  6. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Scored 5.9 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity NoneNo integrity impact
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Simatic Cn 4100 Firmware, not every advisory.