Bug 2396056 (CVE-2025-9232) - CVE-2025-9232 openssl: Out-of-bounds read in HTTP client no_proxy handling
Summary: CVE-2025-9232 openssl: Out-of-bounds read in HTTP client no_proxy handling
Keywords:
Status: NEW
Alias: CVE-2025-9232
Deadline: 2025-09-30
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2400667 2400669 2400671 2400673 2400675 2400679 2400681 2400683 2400685 2400677 2400684
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-09-17 12:22 UTC by OSIDB Bzimport
Modified: 2025-10-02 11:33 UTC (History)
61 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-09-17 12:22:45 UTC
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 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.

OpenSSL 3.5, 3.4, 3.3, 3.2 and 3.0 are vulnerable to this issue.

OpenSSL 1.1.1 and 1.0.2 are not affected by this issue.


Note You need to log in before you can comment on or make changes to this bug.