CVE-2023-2650

Possible DoS translating ASN.1 object identifiers

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 relativ


We have discovered 26,398 live websites that are affected by CVE-2023-2650.

Test my site




Affected Software

Product  OpenSSL
Category Web Server Extensions
Vulnerable Domains26,398 live websites (3.94% of OpenSSL install base)
Vulnerable Versions
  • from 3 before 3.0.9
  • from 3.1.1 before 3.1.1
Vulnerable Versions Count8 versions ( 20.00% of all versions)



Details

  • Published - May 30, 2023
  • Updated - Feb 13, 2025

Credits

  • OSSFuzz (reporter)
  • Matt Caswell (reporter)
  • Richard Levitte (remediation developer)

CVE-2023-2650 usage by Country

United States12,681 websites



France2,384 websites
Germany1,545 websites
Japan1,438 websites
GB891 websites
Canada878 websites
Finland691 websites
Netherlands637 websites
Italy442 websites
Hungary406 websites

CVE-2023-2650 usage by TLD

.com11,569 websites
.org1,241 websites
.net1,154 websites
.jp938 websites
.edu828 websites
.ca741 websites
.co.uk720 websites
.nl558 websites
.fi550 websites
.fr545 websites

Vulnerable Versions

Vulnerable versions are highlighted in red

Websites affected by CVE-2023-2650

Top websites that are affected by CVE-2023-2650. Please click on the "Contact us" link to get more information.
DomainCountryRankContacts
***********.com United States*,***
***.***********.com United States*,***
*******.com United States*,***
******.***************.com United States*,***
****************.com United States**,***
**.***.au Australia**,***
***.edu United States**,***
*********.ch United States**,***
******.org Singapore**,***
********.org France**,***
See full domain list

FAQ

A total of 26,398 websites have been identified as vulnerable to CVE-2023-2650, discovered through global website indexing conducted by WebTechSurvey.
OpenSSL is susceptible to CVE-2023-2650 vulnerability.
OpenSSL versions before 3.1.1 are vulnerable to CVE-2023-2650.
Version 3.1.1 of OpenSSL addresses the CVE-2023-2650 security vulnerability.

References