# CVE-2023-2650: Possible DoS translating ASN.1 object identifiers > Attackers can cause denial of service by sending specially crafted ASN.1 object identifiers that trigger excessive processing delays in OpenSSL. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 30 May 2023 - **Updated:** 14 Oct 2026 - **Also known as:** ALPINE-CVE-2023-2650, AZL-26984, AZL-27009, AZL-31144, AZL-34667, AZL-37674, CLEANSTART-2026-AY81205, CLSA-2023-1687268961, CLSA-2023-1687269261, CLSA-2023-1687269523, CLSA-2023-1687269849, CLSA-2023-1687282015, CLSA-2025-1744368964, DEBIAN-CVE-2023-2650, GHSA-gqxg-9vfr-p9cg, JLSEC-2026-239, MGASA-2023-0195, OESA-2023-1354, OESA-2023-1355, OESA-2023-1356, SUSE-SU-2023:2327-1, SUSE-SU-2023:2328-1, SUSE-SU-2023:2329-1, SUSE-SU-2023:2330-1, SUSE-SU-2023:2331-1, SUSE-SU-2023:2332-1, SUSE-SU-2023:2342-1, SUSE-SU-2023:2343-1, SUSE-SU-2023:2469-1, SUSE-SU-2023:2471-1, UBUNTU-CVE-2023-2650, USN-6188-1, openSUSE-SU-2024:12966-1, openSUSE-SU-2024:12972-1 ## What is CVE-2023-2650? CVE-2023-2650 is a medium-severity denial of service vulnerability in Debian Debian Linux, published on 30 May 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Issue summary: Processing some specially crafted ASN.1 object identifiers or data containing them may be very slow. Impact summary: Applications that use OBJ_obj2txt() directly, or use any of the OpenSSL subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS with no message size limit may experience notable to very long delays when processing those messages, which may lead to a Denial of Service. An OBJECT IDENTIFIER is composed of a series of numbers - sub-identifiers - most of which have no size limit. OBJ_obj2txt() may be used to translate an ASN.1 OBJECT IDENTIFIER given in DER encoding form (using the OpenSSL type ASN1_OBJECT) to its canonical numeric text form, which are the sub-identifiers of the OBJECT IDENTIFIER in decimal form, separated by periods. When one of the sub-identifiers in the OBJECT IDENTIFIER is very large (these are sizes that are seen as absurdly large, taking up tens or hundreds of KiBs), the translation to a decimal number in text may take a very long time. The time complexity is O(n^2) with 'n' being the size of the sub-identifiers in bytes (*). With OpenSSL 3.0, support to fetch cryptographic algorithms using names / identifiers in string form was introduced. This includes using OBJECT IDENTIFIERs in canonical numeric text form as identifiers for fetching algorithms. Such OBJECT IDENTIFIERs may be received through the ASN.1 structure AlgorithmIdentifier, which is commonly used in multiple protocols to specify what cryptographic algorithm should be used to sign or verify, encrypt or decrypt, or digest passed data. Applications that call OBJ_obj2txt() directly with untrusted data are affected, with any version of OpenSSL. If the use is for the mere purpose of display, the severity is considered low. In OpenSSL 3.0 and newer, this affects the subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS. It also impacts anything that processes X.509 certificates, including simple things like verifying its signature. The impact on TLS is relatively low, because all versions of OpenSSL have a 100KiB limit on the peer's certificate chain. Additionally, this only impacts clients, or servers that have explicitly enabled client authentication. In OpenSSL 1.1.1 and 1.0.2, this only affects displaying diverse objects, such as X.509 certificates. This is assumed to not happen in such a way that it would cause a Denial of Service, so these versions are considered not affected by this issue in such a way that it would be cause for concern, and the severity is therefore considered low. Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling) ## Which versions are affected by CVE-2023-2650? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `openssl-1_0_0` | SUSE:Enterprise Storage 7 | All versions | 1.0.2p-150000.3.76.1 | | `openssl-1_1` | SUSE:Enterprise Storage 7 | All versions | 1.1.1d-150200.11.65.1 | | `openssl-1_0_0` | SUSE:Enterprise Storage 7.1 | All versions | 1.0.2p-150000.3.76.1 | | `openssl-1_1` | SUSE:Enterprise Storage 7.1 | All versions | 1.1.1d-150200.11.65.1 | | `openssl-1_1` | SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | All versions | 1.1.0i-150100.14.51.1 | | `openssl-1_1` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 1.1.1d-150200.11.65.1 | | `openssl-1_0_0` | SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOS | All versions | 1.0.2p-150000.3.76.1 | | `openssl-1_1` | SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOS | All versions | 1.1.1d-150200.11.65.1 | | `openssl-1_0_0` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 1.0.2p-150000.3.76.1 | | `openssl-1_1` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 1.1.1d-150200.11.65.1 | | `openssl-1_1` | SUSE:Linux Enterprise Micro 5.1 | All versions | 1.1.1d-150200.11.65.1 | | `openssl-1_1` | SUSE:Linux Enterprise Micro 5.2 | All versions | 1.1.1d-150200.11.65.1 | | `openssl-1_1` | SUSE:Linux Enterprise Micro 5.3 | All versions | 1.1.1l-150400.7.37.1 | | `openssl-1_1` | SUSE:Linux Enterprise Micro 5.4 | All versions | 1.1.1l-150400.7.37.1 | | `openssl-1_1` | SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 1.1.1l-150400.7.37.1 | | `compat-openssl098` | SUSE:Linux Enterprise Module for Legacy 12 | All versions | 0.9.8j-106.51.1 | | `openssl-1_0_0` | SUSE:Linux Enterprise Module for Legacy 15 SP4 | All versions | 1.0.2p-150000.3.76.1 | | `openssl-1_0_0` | SUSE:Linux Enterprise Module for Legacy 15 SP5 | All versions | 1.0.2p-150000.3.76.1 | | `openssl-1_1` | SUSE:Linux Enterprise Real Time 15 SP3 | All versions | 1.1.1d-150200.11.65.1 | | `openssl` | SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | All versions | 0.9.8j-0.106.71.1 | | `openssl1` | SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | All versions | 1.0.1g-0.58.67.1 | | `openssl` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 1.0.2j-60.95.1 | | `openssl-1_0_0` | SUSE:Linux Enterprise Server 12 SP4-ESPOS | All versions | 1.0.2p-3.75.1 | | `openssl-1_1` | SUSE:Linux Enterprise Server 12 SP4-ESPOS | All versions | 1.1.1d-2.84.1 | | `openssl-1_0_0` | SUSE:Linux Enterprise Server 12 SP4-LTSS | All versions | 1.0.2p-3.75.1 | | `openssl-1_1` | SUSE:Linux Enterprise Server 12 SP4-LTSS | All versions | 1.1.1d-2.84.1 | | `openssl-1_0_0` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 1.0.2p-3.75.1 | | `openssl-1_1` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 1.1.1d-2.84.1 | | `openssl-1_0_0` | SUSE:Linux Enterprise Server 15 SP1-LTSS | All versions | 1.0.2p-150000.3.76.1 | | `openssl-1_1` | SUSE:Linux Enterprise Server 15 SP1-LTSS | All versions | 1.1.0i-150100.14.51.1 | | `openssl-1_0_0` | SUSE:Linux Enterprise Server 15 SP2-LTSS | All versions | 1.0.2p-150000.3.76.1 | | `openssl-1_1` | SUSE:Linux Enterprise Server 15 SP2-LTSS | All versions | 1.1.1d-150200.11.65.1 | | `openssl-1_0_0` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 1.0.2p-150000.3.76.1 | | `openssl-1_1` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 1.1.1d-150200.11.65.1 | | `compat-openssl098` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 0.9.8j-106.51.1 | | `openssl-1_0_0` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 1.0.2p-3.75.1 | | `openssl-1_1` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 1.1.1d-2.84.1 | | `compat-openssl098` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 0.9.8j-106.51.1 | | `openssl-1_0_0` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 1.0.2p-3.75.1 | | `openssl-1_1` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 1.1.1d-2.84.1 | Products: Debian Debian Linux, Openssl Openssl. ## How do I fix CVE-2023-2650? Apply the vendor's patch. ## Is CVE-2023-2650 being exploited? There is no known exploitation of CVE-2023-2650 in the wild and no public exploit code. ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-2650 and fix it if it is affected. What it is: CVE-2023-2650 is a medium-severity denial of service vulnerability in Debian Debian Linux, published on 30 May 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2023-2650 in the wild and no public exploit code. Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-2650/ (Markdown: https://insights.sbomify.com/CVE-2023-2650/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-2650 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-2650 - OSV: https://osv.dev/vulnerability/CVE-2023-2650 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-2650/ Summaries are generated and may contain mistakes; the official description above is the record.