AIKIDO-2026-740956
erlang is vulnerable to Denial of Service (DoS)
82
CVE Score
High
Denial of Service (DoS)
TL;DR
asn1rtt_ber:dec_subidentifiers/3, asn1rtt_per_common:dec_subidentifiers/3, and asn1rtt_jer:json2oid/1 accumulate a base-128 OBJECT IDENTIFIER subidentifier into an unbounded integer with (Av bsl 7) + H per continuation byte. Each shift and addition is linear in the bits already accumulated, so one oversized arc is quadratic CPU work. That decoder is generated into every ASN.1 module that contains an OBJECT IDENTIFIER, including OTP-PUB-KEY reached from public_key:pkix_decode_cert/2 before signature verification, so a crafted peer certificate during a TLS handshake with verify_peer can stall the process. The fix bounds OID arc decoding so a large subidentifier cannot consume superlinear CPU.
How do I fix this?
Upgrade the erlang library to the patch version.
Who does this affect?
You are affected if you are using a version that falls within the vulnerable range and you decode untrusted ASN.1 OBJECT IDENTIFIERs, including TLS with the verify_peer option.
Package
erlangVersions
17.0.0 - 27.3.4.17
Fixed in 27.3.4.1828.0.0 - 28.5.0.6
Fixed in 28.5.0.729.0.0 - 29.1
Fixed in 29.1.1Background info
erlang is vulnerable to Denial of Service (DoS) in versions 17.0.0 - 27.3.4.17, 28.0.0 - 28.5.0.6 and 29.0.0 - 29.1.
Links
Get secure today,
quickly and for free.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPAuthorized© All Intel data is openly available and commercially licensed.