cve-2025-9232
Vulnerability from cvelistv5
Published
2025-09-30 13:17
Modified
2025-09-30 19:22
Severity ?
EPSS score ?
Summary
Out-of-bounds read in HTTP client no_proxy handling
References
{ "containers": { "adp": [ { "metrics": [ { "cvssV3_1": { "attackComplexity": "HIGH", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "baseScore": 5.9, "baseSeverity": "MEDIUM", "confidentialityImpact": "NONE", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H", "version": "3.1" } }, { "other": { "content": { "id": "CVE-2025-9232", "options": [ { "Exploitation": "none" }, { "Automatable": "no" }, { "Technical Impact": "partial" } ], "role": "CISA Coordinator", "timestamp": "2025-09-30T19:22:31.407504Z", "version": "2.0.3" }, "type": "ssvc" } } ], "providerMetadata": { "dateUpdated": "2025-09-30T19:22:35.483Z", "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP" }, "title": "CISA ADP Vulnrichment" } ], "cna": { "affected": [ { "defaultStatus": "unaffected", "product": "OpenSSL", "vendor": "OpenSSL", "versions": [ { "lessThan": "3.5.4", "status": "affected", "version": "3.5.0", "versionType": "semver" }, { "lessThan": "3.4.3", "status": "affected", "version": "3.4.0", "versionType": "semver" }, { "lessThan": "3.3.5", "status": "affected", "version": "3.3.3", "versionType": "semver" }, { "lessThan": "3.2.6", "status": "affected", "version": "3.2.4", "versionType": "semver" }, { "lessThan": "3.0.18", "status": "affected", "version": "3.0.16", "versionType": "semver" } ] } ], "credits": [ { "lang": "en", "type": "reporter", "value": "Stanislav Fort (Aisle Research)" }, { "lang": "en", "type": "remediation developer", "value": "Stanislav Fort (Aisle Research)" } ], "datePublic": "2025-09-30T14:00:00.000Z", "descriptions": [ { "lang": "en", "supportingMedia": [ { "base64": false, "type": "text/html", "value": "Issue summary: An application using the OpenSSL HTTP client API functions may\u003cbr\u003etrigger an out-of-bounds read if the \u0027no_proxy\u0027 environment variable is set and\u003cbr\u003ethe host portion of the authority component of the HTTP URL is an IPv6 address.\u003cbr\u003e\u003cbr\u003eImpact summary: An out-of-bounds read can trigger a crash which leads to\u003cbr\u003eDenial of Service for an application.\u003cbr\u003e\u003cbr\u003eThe OpenSSL HTTP client API functions can be used directly by applications\u003cbr\u003ebut they are also used by the OCSP client functions and CMP (Certificate\u003cbr\u003eManagement Protocol) client implementation in OpenSSL. However the URLs used\u003cbr\u003eby these implementations are unlikely to be controlled by an attacker.\u003cbr\u003e\u003cbr\u003eIn this vulnerable code the out of bounds read can only trigger a crash.\u003cbr\u003eFurthermore the vulnerability requires an attacker-controlled URL to be\u003cbr\u003epassed from an application to the OpenSSL function and the user has to have\u003cbr\u003ea \u0027no_proxy\u0027 environment variable set. For the aforementioned reasons the\u003cbr\u003eissue was assessed as Low severity.\u003cbr\u003e\u003cbr\u003eThe vulnerable code was introduced in the following patch releases:\u003cbr\u003e3.0.16, 3.1.8, 3.2.4, 3.3.3, 3.4.0 and 3.5.0.\u003cbr\u003e\u003cbr\u003eThe FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this\u003cbr\u003eissue, as the HTTP client implementation is outside the OpenSSL FIPS module\u003cbr\u003eboundary." } ], "value": "Issue summary: An application using the OpenSSL HTTP client API functions may\ntrigger an out-of-bounds read if the \u0027no_proxy\u0027 environment variable is set and\nthe host portion of the authority component of the HTTP URL is an IPv6 address.\n\nImpact summary: An out-of-bounds read can trigger a crash which leads to\nDenial of Service for an application.\n\nThe OpenSSL HTTP client API functions can be used directly by applications\nbut they are also used by the OCSP client functions and CMP (Certificate\nManagement Protocol) client implementation in OpenSSL. However the URLs used\nby these implementations are unlikely to be controlled by an attacker.\n\nIn this vulnerable code the out of bounds read can only trigger a crash.\nFurthermore the vulnerability requires an attacker-controlled URL to be\npassed from an application to the OpenSSL function and the user has to have\na \u0027no_proxy\u0027 environment variable set. For the aforementioned reasons the\nissue was assessed as Low severity.\n\nThe vulnerable code was introduced in the following patch releases:\n3.0.16, 3.1.8, 3.2.4, 3.3.3, 3.4.0 and 3.5.0.\n\nThe FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this\nissue, as the HTTP client implementation is outside the OpenSSL FIPS module\nboundary." } ], "metrics": [ { "format": "other", "other": { "content": { "text": "Low" }, "type": "https://openssl-library.org/policies/general/security-policy/" } } ], "problemTypes": [ { "descriptions": [ { "cweId": "CWE-125", "description": "CWE-125 Out-of-bounds Read", "lang": "en", "type": "CWE" } ] } ], "providerMetadata": { "dateUpdated": "2025-09-30T13:17:19.172Z", "orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5", "shortName": "openssl" }, "references": [ { "name": "OpenSSL Advisory", "tags": [ "vendor-advisory" ], "url": "https://openssl-library.org/news/secadv/20250930.txt" }, { "name": "3.5.4 git commit", "tags": [ "patch" ], "url": "https://github.com/openssl/openssl/commit/2b4ec20e47959170422922eaff25346d362dcb35" }, { "name": "3.4.3 git commit", "tags": [ "patch" ], "url": "https://github.com/openssl/openssl/commit/7cf21a30513c9e43c4bc3836c237cf086e194af3" }, { "name": "3.3.5 git commit", "tags": [ "patch" ], "url": "https://github.com/openssl/openssl/commit/bbf38c034cdabd0a13330abcc4855c866f53d2e0" }, { "name": "3.2.6 git commit", "tags": [ "patch" ], "url": "https://github.com/openssl/openssl/commit/89e790ac431125a4849992858490bed6b225eadf" }, { "name": "3.0.18 git commit", "tags": [ "patch" ], "url": "https://github.com/openssl/openssl/commit/654dc11d23468a74fc8ea4672b702dd3feb7be4b" } ], "source": { "discovery": "UNKNOWN" }, "title": "Out-of-bounds read in HTTP client no_proxy handling", "x_generator": { "engine": "Vulnogram 0.2.0" } } }, "cveMetadata": { "assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5", "assignerShortName": "openssl", "cveId": "CVE-2025-9232", "datePublished": "2025-09-30T13:17:19.172Z", "dateReserved": "2025-08-20T08:38:12.019Z", "dateUpdated": "2025-09-30T19:22:35.483Z", "state": "PUBLISHED" }, "dataType": "CVE_RECORD", "dataVersion": "5.1", "meta": { "nvd": "{\"cve\":{\"id\":\"CVE-2025-9232\",\"sourceIdentifier\":\"openssl-security@openssl.org\",\"published\":\"2025-09-30T14:15:41.313\",\"lastModified\":\"2025-09-30T20:15:41.397\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"Issue summary: An application using the OpenSSL HTTP client API functions may\\ntrigger an out-of-bounds read if the \u0027no_proxy\u0027 environment variable is set and\\nthe host portion of the authority component of the HTTP URL is an IPv6 address.\\n\\nImpact summary: An out-of-bounds read can trigger a crash which leads to\\nDenial of Service for an application.\\n\\nThe OpenSSL HTTP client API functions can be used directly by applications\\nbut they are also used by the OCSP client functions and CMP (Certificate\\nManagement Protocol) client implementation in OpenSSL. However the URLs used\\nby these implementations are unlikely to be controlled by an attacker.\\n\\nIn this vulnerable code the out of bounds read can only trigger a crash.\\nFurthermore the vulnerability requires an attacker-controlled URL to be\\npassed from an application to the OpenSSL function and the user has to have\\na \u0027no_proxy\u0027 environment variable set. For the aforementioned reasons the\\nissue was assessed as Low severity.\\n\\nThe vulnerable code was introduced in the following patch releases:\\n3.0.16, 3.1.8, 3.2.4, 3.3.3, 3.4.0 and 3.5.0.\\n\\nThe FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this\\nissue, as the HTTP client implementation is outside the OpenSSL FIPS module\\nboundary.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":5.9,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"HIGH\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":2.2,\"impactScore\":3.6}]},\"weaknesses\":[{\"source\":\"openssl-security@openssl.org\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-125\"}]}],\"references\":[{\"url\":\"https://github.com/openssl/openssl/commit/2b4ec20e47959170422922eaff25346d362dcb35\",\"source\":\"openssl-security@openssl.org\"},{\"url\":\"https://github.com/openssl/openssl/commit/654dc11d23468a74fc8ea4672b702dd3feb7be4b\",\"source\":\"openssl-security@openssl.org\"},{\"url\":\"https://github.com/openssl/openssl/commit/7cf21a30513c9e43c4bc3836c237cf086e194af3\",\"source\":\"openssl-security@openssl.org\"},{\"url\":\"https://github.com/openssl/openssl/commit/89e790ac431125a4849992858490bed6b225eadf\",\"source\":\"openssl-security@openssl.org\"},{\"url\":\"https://github.com/openssl/openssl/commit/bbf38c034cdabd0a13330abcc4855c866f53d2e0\",\"source\":\"openssl-security@openssl.org\"},{\"url\":\"https://openssl-library.org/news/secadv/20250930.txt\",\"source\":\"openssl-security@openssl.org\"}]}}" } }
Loading...
Loading...
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.