From 013cbc0697eacd5460014872da7c916b1639d807 Mon Sep 17 00:00:00 2001 From: Tomas Mraz Date: Tue, 30 Sep 2025 14:58:32 +0200 Subject: [PATCH] Add JSON and secadv file for September 30th 2025 release --- secadv/20250930.txt | 146 +++++++++++++++++++++++++++ secjson/CVE-2025-9230.json | 195 +++++++++++++++++++++++++++++++++++++ secjson/CVE-2025-9231.json | 150 ++++++++++++++++++++++++++++ secjson/CVE-2025-9232.json | 158 ++++++++++++++++++++++++++++++ 4 files changed, 649 insertions(+) create mode 100644 secadv/20250930.txt create mode 100644 secjson/CVE-2025-9230.json create mode 100644 secjson/CVE-2025-9231.json create mode 100644 secjson/CVE-2025-9232.json diff --git a/secadv/20250930.txt b/secadv/20250930.txt new file mode 100644 index 0000000..641c632 --- /dev/null +++ b/secadv/20250930.txt @@ -0,0 +1,146 @@ +OpenSSL Security Advisory [30th September 2025] +=============================================== + +Out-of-bounds read & write in RFC 3211 KEK Unwrap (CVE-2025-9230) +================================================================= + +Severity: Moderate + +Issue summary: An application trying to decrypt CMS messages encrypted using +password based encryption can trigger an out-of-bounds read and write. + +Impact summary: This out-of-bounds read may trigger a crash which leads to +Denial of Service for an application. The out-of-bounds write can cause +a memory corruption which can have various consequences including +a Denial of Service or Execution of attacker-supplied code. + +Although the consequences of a successful exploit of this vulnerability +could be severe, the probability that the attacker would be able to +perform it is low. Besides, password based (PWRI) encryption support in CMS +messages is very rarely used. For that reason the issue was assessed as +Moderate severity according to our Security Policy. + +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 CMS implementation is outside the OpenSSL FIPS module +boundary. + +OpenSSL 3.5, 3.4, 3.3, 3.2, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue. + +OpenSSL 3.5 users should upgrade to OpenSSL 3.5.4. + +OpenSSL 3.4 users should upgrade to OpenSSL 3.4.3. + +OpenSSL 3.3 users should upgrade to OpenSSL 3.3.5. + +OpenSSL 3.2 users should upgrade to OpenSSL 3.2.6. + +OpenSSL 3.0 users should upgrade to OpenSSL 3.0.18. + +OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1zd. +(premium support customers only) + +OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zm. +(premium support customers only) + +This issue was reported on 9th August 2025 by Stanislav Fort (Aisle Research). +The fix was developed by Stanislav Fort (Aisle Research) and Viktor Dukhovni. + + +Timing side-channel in SM2 algorithm on 64 bit ARM (CVE-2025-9231) +================================================================= + +Severity: Moderate + +Issue summary: A timing side-channel which could potentially allow remote +recovery of the private key exists in the SM2 algorithm implementation on 64 bit +ARM platforms. + +Impact summary: A timing side-channel in SM2 signature computations on 64 bit +ARM platforms could allow recovering the private key by an attacker. + +While remote key recovery over a network was not attempted by the reporter, +timing measurements revealed a timing signal which may allow such an attack. + +OpenSSL does not directly support certificates with SM2 keys in TLS, and so +this CVE is not relevant in most TLS contexts. However, given that it is +possible to add support for such certificates via a custom provider, coupled +with the fact that in such a custom provider context the private key may be +recoverable via remote timing measurements, we consider this to be a Moderate +severity issue. + +The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this +issue, as SM2 is not an approved algorithm. + +OpenSSL 3.1, 3.0, 1.1.1 and 1.0.2 are not vulnerable to this issue. + +OpenSSL 3.5, 3.4, 3.3, and 3.2 are vulnerable to this issue. + +OpenSSL 3.5 users should upgrade to OpenSSL 3.5.4. + +OpenSSL 3.4 users should upgrade to OpenSSL 3.4.3. + +OpenSSL 3.3 users should upgrade to OpenSSL 3.3.5. + +OpenSSL 3.2 users should upgrade to OpenSSL 3.2.6. + +This issue was reported on 18th August 2025 by Stanislav Fort (Aisle Research) +The fix was developed by Stanislav Fort. + +Out-of-bounds read in HTTP client no_proxy handling (CVE-2025-9232) +=================================================================== + +Severity: Low + +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. + +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. + +OpenSSL 3.5 users should upgrade to OpenSSL 3.5.4. + +OpenSSL 3.4 users should upgrade to OpenSSL 3.4.3. + +OpenSSL 3.3 users should upgrade to OpenSSL 3.3.5. + +OpenSSL 3.2 users should upgrade to OpenSSL 3.2.6. + +OpenSSL 3.0 users should upgrade to OpenSSL 3.0.18. + +This issue was reported on 16th August 2025 by Stanislav Fort (Aisle Research). +The fix was developed by Stanislav Fort (Aisle Research). + +General Advisory Notes +====================== + +URL for this Security Advisory: +https://openssl-library.org/news/secadv/20250930.txt + +Note: the online version of the advisory may be updated with additional details +over time. + +For details of OpenSSL severity classifications please see: +https://openssl-library.org/policies/general/security-policy/ diff --git a/secjson/CVE-2025-9230.json b/secjson/CVE-2025-9230.json new file mode 100644 index 0000000..f99d8ae --- /dev/null +++ b/secjson/CVE-2025-9230.json @@ -0,0 +1,195 @@ +{ + "containers": { + "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.0", + "versionType": "semver" + }, + { + "lessThan": "3.2.6", + "status": "affected", + "version": "3.2.0", + "versionType": "semver" + }, + { + "lessThan": "3.0.18", + "status": "affected", + "version": "3.0.0", + "versionType": "semver" + }, + { + "lessThan": "1.1.1zd", + "status": "affected", + "version": "1.1.1", + "versionType": "custom" + }, + { + "lessThan": "1.0.2zm", + "status": "affected", + "version": "1.0.2", + "versionType": "custom" + } + ] + } + ], + "credits": [ + { + "lang": "en", + "type": "reporter", + "value": "Stanislav Fort (Aisle Research)" + }, + { + "lang": "en", + "type": "remediation developer", + "value": "Stanislav Fort (Aisle Research)" + }, + { + "lang": "en", + "type": "remediation developer", + "value": "Viktor Dukhovni" + } + ], + "datePublic": "2025-09-30T14:00:00.000Z", + "descriptions": [ + { + "lang": "en", + "supportingMedia": [ + { + "base64": false, + "type": "text/html", + "value": "Issue summary: An application trying to decrypt CMS messages encrypted using
password based encryption can trigger an out-of-bounds read and write.

Impact summary: This out-of-bounds read may trigger a crash which leads to
Denial of Service for an application. The out-of-bounds write can cause
a memory corruption which can have various consequences including
a Denial of Service or Execution of attacker-supplied code.

Although the consequences of a successful exploit of this vulnerability
could be severe, the probability that the attacker would be able to
perform it is low. Besides, password based (PWRI) encryption support in CMS
messages is very rarely used. For that reason the issue was assessed as
Moderate severity according to our Security Policy.

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 CMS implementation is outside the OpenSSL FIPS module
boundary." + } + ], + "value": "Issue summary: An application trying to decrypt CMS messages encrypted using\npassword based encryption can trigger an out-of-bounds read and write.\n\nImpact summary: This out-of-bounds read may trigger a crash which leads to\nDenial of Service for an application. The out-of-bounds write can cause\na memory corruption which can have various consequences including\na Denial of Service or Execution of attacker-supplied code.\n\nAlthough the consequences of a successful exploit of this vulnerability\ncould be severe, the probability that the attacker would be able to\nperform it is low. Besides, password based (PWRI) encryption support in CMS\nmessages is very rarely used. For that reason the issue was assessed as\nModerate severity according to our Security Policy.\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 CMS implementation is outside the OpenSSL FIPS module\nboundary." + } + ], + "metrics": [ + { + "format": "other", + "other": { + "content": { + "text": "Moderate" + }, + "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" + }, + { + "cweId": "CWE-787", + "description": "CWE-787 Out-of-bounds Write", + "lang": "en", + "type": "CWE" + } + ] + } + ], + "providerMetadata": { + "orgId": "00000000-0000-4000-9000-000000000000", + "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/bae259a211ada6315dc50900686daaaaaa55f482" + }, + { + "name": "3.4.3 git commit", + "tags": [ + "patch" + ], + "url": "https://github.com/openssl/openssl/commit/9e91358f365dee6c446dcdcdb01c04d2743fd280" + }, + { + "name": "3.3.5 git commit", + "tags": [ + "patch" + ], + "url": "https://github.com/openssl/openssl/commit/5965ea5dd6960f36d8b7f74f8eac67a8eb8f2b45" + }, + { + "name": "3.2.6 git commit", + "tags": [ + "patch" + ], + "url": "https://github.com/openssl/openssl/commit/b5282d677551afda7d20e9c00e09561b547b2dfd" + }, + { + "name": "3.0.18 git commit", + "tags": [ + "patch" + ], + "url": "https://github.com/openssl/openssl/commit/a79c4ce559c6a3a8fd4109e9f33c1185d5bf2def" + }, + { + "name": "1.1.1zd git commit", + "tags": [ + "patch" + ], + "url": "https://github.openssl.org/openssl/extended-releases/commit/dfbaf161d8dafc1132dd88cd48ad990ed9b4c8ba" + }, + { + "name": "1.0.2zm git commit", + "tags": [ + "patch" + ], + "url": "https://github.openssl.org/openssl/extended-releases/commit/c2b96348bfa662f25f4fabf81958ae822063dae3" + } + ], + "source": { + "discovery": "UNKNOWN" + }, + "title": "Out-of-bounds read & write in RFC 3211 KEK Unwrap", + "x_generator": { + "engine": "Vulnogram 0.2.0" + } + } + }, + "cveMetadata": { + "assignerOrgId": "00000000-0000-4000-9000-000000000000", + "cveId": "CVE-2025-9230", + "requesterUserId": "00000000-0000-4000-9000-000000000000", + "serial": 1, + "state": "PUBLISHED" + }, + "dataType": "CVE_RECORD", + "dataVersion": "5.1" +} diff --git a/secjson/CVE-2025-9231.json b/secjson/CVE-2025-9231.json new file mode 100644 index 0000000..2b67446 --- /dev/null +++ b/secjson/CVE-2025-9231.json @@ -0,0 +1,150 @@ +{ + "containers": { + "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.0", + "versionType": "semver" + }, + { + "lessThan": "3.2.6", + "status": "affected", + "version": "3.2.0", + "versionType": "semver" + } + ] + } + ], + "credits": [ + { + "lang": "en", + "type": "reporter", + "value": "Stanislav Fort (Aisle Research)" + }, + { + "lang": "en", + "type": "remediation developer", + "value": "Stanislav Fort (Aisle Research)" + }, + { + "lang": "en", + "type": "remediation developer", + "value": "Tomas Mraz" + } + ], + "datePublic": "2025-09-30T14:00:00.000Z", + "descriptions": [ + { + "lang": "en", + "supportingMedia": [ + { + "base64": false, + "type": "text/html", + "value": "Issue summary: A timing side-channel which could potentially allow remote
recovery of the private key exists in the SM2 algorithm implementation on 64 bit
ARM platforms.

Impact summary: A timing side-channel in SM2 signature computations on 64 bit
ARM platforms could allow recovering the private key by an attacker..

While remote key recovery over a network was not attempted by the reporter,
timing measurements revealed a timing signal which may allow such an attack.

OpenSSL does not directly support certificates with SM2 keys in TLS, and so
this CVE is not relevant in most TLS contexts. However, given that it is
possible to add support for such certificates via a custom provider, coupled
with the fact that in such a custom provider context the private key may be
recoverable via remote timing measurements, we consider this to be a Moderate
severity issue.

The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this
issue, as SM2 is not an approved algorithm." + } + ], + "value": "Issue summary: A timing side-channel which could potentially allow remote\nrecovery of the private key exists in the SM2 algorithm implementation on 64 bit\nARM platforms.\n\nImpact summary: A timing side-channel in SM2 signature computations on 64 bit\nARM platforms could allow recovering the private key by an attacker..\n\nWhile remote key recovery over a network was not attempted by the reporter,\ntiming measurements revealed a timing signal which may allow such an attack.\n\nOpenSSL does not directly support certificates with SM2 keys in TLS, and so\nthis CVE is not relevant in most TLS contexts. However, given that it is\npossible to add support for such certificates via a custom provider, coupled\nwith the fact that in such a custom provider context the private key may be\nrecoverable via remote timing measurements, we consider this to be a Moderate\nseverity issue.\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 SM2 is not an approved algorithm." + } + ], + "metrics": [ + { + "format": "other", + "other": { + "content": { + "text": "Moderate" + }, + "type": "https://openssl-library.org/policies/general/security-policy/" + } + } + ], + "problemTypes": [ + { + "descriptions": [ + { + "cweId": "CWE-385", + "description": "CWE-385 Covert Timing Channel", + "lang": "en", + "type": "CWE" + } + ] + } + ], + "providerMetadata": { + "orgId": "00000000-0000-4000-9000-000000000000", + "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/fc47a2ec078912b3e914fab5734535e76c4820c2" + }, + { + "name": "3.4.3 git commit", + "tags": [ + "patch" + ], + "url": "https://github.com/openssl/openssl/commit/eed5adc9f969d77c94f213767acbb41ff923b6f4" + }, + { + "name": "3.3.5 git commit", + "tags": [ + "patch" + ], + "url": "https://github.com/openssl/openssl/commit/567f64386e43683888212226824b6a179885a0fe" + }, + { + "name": "3.2.6 git commit", + "tags": [ + "patch" + ], + "url": "https://github.com/openssl/openssl/commit/cba616c26ac8e7b37de5e77762e505ba5ca51698" + } + ], + "source": { + "discovery": "UNKNOWN" + }, + "title": "Timing side-channel in SM2 algorithm on 64 bit ARM", + "x_generator": { + "engine": "Vulnogram 0.2.0" + } + } + }, + "cveMetadata": { + "assignerOrgId": "00000000-0000-4000-9000-000000000000", + "cveId": "CVE-2025-9231", + "requesterUserId": "00000000-0000-4000-9000-000000000000", + "serial": 1, + "state": "PUBLISHED" + }, + "dataType": "CVE_RECORD", + "dataVersion": "5.1" +} diff --git a/secjson/CVE-2025-9232.json b/secjson/CVE-2025-9232.json new file mode 100644 index 0000000..b7900bc --- /dev/null +++ b/secjson/CVE-2025-9232.json @@ -0,0 +1,158 @@ +{ + "containers": { + "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
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." + } + ], + "value": "Issue summary: An application using the OpenSSL HTTP client API functions may\ntrigger an out-of-bounds read if the 'no_proxy' 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 'no_proxy' 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": { + "orgId": "00000000-0000-4000-9000-000000000000", + "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": "00000000-0000-4000-9000-000000000000", + "cveId": "CVE-2025-9232", + "requesterUserId": "00000000-0000-4000-9000-000000000000", + "serial": 1, + "state": "PUBLISHED" + }, + "dataType": "CVE_RECORD", + "dataVersion": "5.1" +}