VulnerabilityPublished 10 Feb 2025Updated 5 Nov 2026

CVE-2024-12133: libtasn1 · Inefficient Algorithmic Complexity

Affects libtasn1Source GCVE Database

Compare

Not known to be exploited · CVSS 5.3 Medium.

Data as of 5 Nov 2026, 13:03 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (redhat)	CVSS 3.1	5.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Feb 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubgnutls/libtasn1`pkg:github/gnutls/libtasn1`Other threats	Affected =0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Red Hat has released an official security update for libtasn1 that fixes this vulnerability. Applying the updated packages for Red Hat Enterprise Linux 9.2 and related variants fully mitigates the issue. Users should follow Red Hat's update instructions at https://access.redhat.com/articles/11258 to apply the patch. No additional workarounds or mitigations are indicated by the vendor.

Description

CVE-2024-12133 is a vulnerability in libtasn1 involving inefficient handling of certain certificate data. This inefficiency causes the library to take significantly longer to process certificates with many elements, potentially leading to system slowdown or crash. An attacker can exploit this by sending a specially crafted certificate to trigger a denial of service (DoS). The issue has a moderate severity rating with a CVSS score of 5.3. Red Hat has released patches addressing this vulnerability in libtasn1 for Red Hat Enterprise Linux 9.2 and related variants.

Impact

An attacker can cause a denial of service by sending specially crafted certificates that trigger inefficient processing in libtasn1. This can slow down or crash affected systems. There is no impact on confidentiality or integrity, only availability is affected. Exploitation does not require privileges or user interaction.

Summary

The vulnerability CVE-2024-12133 in libtasn1 is due to inefficient algorithmic complexity when decoding DER-encoded ASN.1 certificate data containing a large number of elements. This inefficiency can cause excessive processing time, leading to denial of service conditions such as system slowdown or crash. The flaw is exploitable remotely without authentication or user interaction by sending a maliciously crafted certificate. Red Hat's advisory confirms the issue and provides updated libtasn1 packages that fix the problem in Red Hat Enterprise Linux 9.2 variants.

CWE-407Inefficient Algorithmic Complexity (opens in a new tab)
Class weaknessLikelihood of exploit: Low
An algorithm in a product has an inefficient worst-case computational complexity that may be detrimental to system performance and can be triggered by an attacker, typically using crafted manipulations that ensure that the worst case is being reached.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Nov 2026, 13:03 UTC

WeaknessesCWE-407

Technical details

References

Community reviews

Related threats