QID 355550

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.
( CVE-2023-2650)

Successful exploitation of this vulnerability could lead to a securitybreach or could affect integrity, availability, and confidentiality.