Skip to main content
← All vulnerabilities
CVE-2026-70409

eldap does not bound the port component of a referral URL before integer conversion

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 27.3.4.17, 28.5.0.6, 29.0.6, 1.2.14.2, 1.2.16.1, and 1 more
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

Improper Validation of Specified Quantity in Input vulnerability in Erlang/OTP eldap allows a malicious or compromised LDAP server to degrade availability by returning a referral URL whose port component is a very long run of digits. eldap:parse_port/2 passes the port substring straight to list_to_integer/1 with no length bound. The surrounding try ... catch only rejects a value that fails to parse, so a syntactically valid port of up to roughly 1.26 million digits converts successfully and costs the caller hundreds of milliseconds of arbitrary-precision arithmetic per referral. The conversion function itself is documented to accept integers of any size, so bounding the input is the caller's responsibility. Reaching the flaw requires the application to pass a server-supplied referral to eldap:parse_ldap_url/1, which eldap never calls itself: referral strings are returned to the caller unparsed. This issue affects OTP from OTP 17.0 before OTP 27.3.4.17, from OTP 28.0 before OTP 28.5.0.6, and from OTP 29.0 before OTP 29.0.6, corresponding to eldap from 1.0.3 before 1.2.14.2, from 1.2.15 before 1.2.16.1, and from 1.3 before 1.3.1.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  3. Record last updated

Affected versions

  • otp

    From 17.0 · fixed in 27.3.4.17; From 28.0 · fixed in 28.5.0.6; From 29.0 · fixed in 29.0.6

  • eldap

    From 1.0.3 · fixed in 1.2.14.2; From 1.2.15 · fixed in 1.2.16.1; From 1.3 · fixed in 1.3.1

  • erlang/otp

    Version range not reported

References 6

GitHub · erlang/otp

cna.erlef.org

osv.dev

erlang.org