Skip to main content
No exploitation reportedFix available

CVE-2023-2650

No exploitation reported by the sources we read.

  • Published2023-05-30
  • Fixed in3.1.1 · 3.0.9 · 1.1.1u · 1.0.2zh
  • WeaknessCWE-770

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2023-05-3014:15CVE publishedNVD
  2. 2026-10-2319:23EPSS crossed 10 %FIRST EPSS

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2023-2650?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2023-2650?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
OpenSSL
BranchAffectedFixed in
3.1≥ 3.1.0, < 3.1.13.1.1
3.0≥ 3.0.0, < 3.0.93.0.9
1.1≥ 1.1.1, < 1.1.1u1.1.1u
1.0≥ 1.0.2, < 1.0.2zh1.0.2zh
Debian debian linux
BranchAffectedFixed in
10.0= 10.0no fix published
11.0= 11.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • ICSA-24-184-03 CISA10 known affected

    Mitsubishi Electric Iconics Digital Solutions and Mitsubishi Electric Products (Update E)

    Mitsubishi Electric Iconics Digital Solutions ICONICS Suite: 10.97.2 · Mitsubishi Electric Iconics Digital Solutions GENESIS64: 10.97.2 · Mitsubishi Electric Iconics Digital Solutions Hyper Historian: 10.97.2 · +7 more

  • ICSA-24-158-03 CISA2 known affected

    Mitsubishi Electric CC-Link IE TSN Industrial Managed Switch

    Mitsubishi Electric NZ2MHG-TSNT8F2: <=05 · Mitsubishi Electric NZ2MHG-TSNT4: <=05

  • ICSA-23-320-08 CISA71 known affected

    Siemens SCALANCE Family Products

    SCALANCE XB205-3 (SC, PN) (6GK5205-3BB00-2AB2) · SCALANCE XB205-3 (ST, E/IP) (6GK5205-3BB00-2TB2) · SCALANCE XB205-3 (ST, E/IP) (6GK5205-3BD00-2TB2) · +68 more

Full record on NVD

Fix

  1. Update OpenSSL to 3.1.1 · 3.0.9 · 1.1.1u · 1.0.2zh
  2. Vendor fix CISA ICSA-24-184-03 · 5 productsMitsubishi Electric Iconics Digital Solutions is releasing fixed version 10.97.3 or later for GENESIS64, ICONICS Suite, Hyper Historian, AnalytiX, and MobileHMI Please download the fixed version from the link "https://iconicsinc.my.site.com/community/s/iconics-software/ICONICS_Software__c/00BQQ0000…
  3. Vendor fix CISA ICSA-24-184-03 · 5 productsMitsubishi Electric is releasing fixed version 10.97.3 or later for GENESIS64, ICONICS Suite, Hyper Historian, AnalytiX, and MobileHMI. Please download the fixed version from the link "https://iconicsinc.my.site.com/community/s/iconics-software/ICONICS_Software__c/00BQQ000008P51V2AS?ICONICS_Softwar…
  4. Vendor fix CISA ICSA-24-158-03 · 1 productCC-Link IE TSN Industrial Managed Switch NZ2MHG-TSNT8F2: Version "06" or later
  5. Vendor fix CISA ICSA-24-158-03 · 1 productCC-Link IE TSN Industrial Managed Switch NZ2MHG-TSNT4: Version "06" or later
  6. Vendor fix CISA ICSA-24-158-03 · 2 productsAfter logging into NZ2MHG-TSNT8F2 or NZ2MHG-TSNT4 through the web interface, update the firmware to the fixed firmware version file mentioned in the above 1 by the function of [System] -> [System Management] -> [Firmware Upgrade] from Function menu. For the detailed procedures, please refer to "CC-…
  7. Vendor fix CISA ICSA-23-320-08 · 71 productsUpdate to V4.5 or later version

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • CISA-ADPSSVC decisionnone2025-03-06
  • OpenCVESSVC decisionnone—
  • CISA-ADPCVSS 3.16.52025-03-06
  • NVDCVSS 3.16.5read 2026-10-23
  • CISA-ADPweakness (CWE)CWE-7702025-03-06
  • NVDweakness (CWE)CWE-770read 2026-10-23
  • FIRST EPSSEPSS score75.4 %read 2026-10-23

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Published
2023-05-30
Last Modified
2026-10-14
NVD status
Modified

Frequently asked questions

What is CVE-2023-2650?

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.

Is CVE-2023-2650 actively exploited?

Active exploitation of CVE-2023-2650 has not been confirmed. Its EPSS score was 75.4% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2023-2650?

CVE-2023-2650 has a CVSS v3 base score of 6.5 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database