erl_tar:extract/2 loops forever on a GNU sparse member with a trailing hole
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.28.0, 0.20.1, 29.1.2, 8.1.1, 2.5.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in Erlang OTP stdlib (erl_tar module), hexpm hex_core (hex_erl_tar module), hexpm hex (mix_hex_erl_tar module) and erlang rebar3 (r3_hex_erl_tar module) allows an attacker who supplies a tar archive to cause a denial of service via a crafted GNU sparse member. When erl_tar:extract/1,2 writes a member to disk, erl_tar:stream_to_file_loop/3 reads it in chunks of 65536 bytes by default. For a GNU sparse member whose sparse map ends before its real size, erl_tar:do_sparse_read/3 matches its trailing-hole clause before its zero-length clause. After the chunk is used up, the trailing-hole clause reads zero bytes, does not advance the position, and recurses forever. A 2048-byte archive keeps the extracting process and one scheduler busy until the process is killed. The {max_size, N} option prevents this only when N is below the real size of the member. Extraction with the memory option is not affected. hex_core ships its own copy of erl_tar as hex_erl_tar, and Hex and rebar3 ship hex_core with prefixed module names (mix_hex_erl_tar and r3_hex_erl_tar). These copies contain the same code and do not call stdlib's erl_tar, so they are affected on any OTP version. OTP 28 is not affected, but an application running on OTP 28 is affected if it extracts archives through an affected version of hex_core, Hex or rebar3. This issue affects OTP from OTP 29.0 before OTP 29.1.2, corresponding to rebar3 from 3.27.1 before 3.28.0, and stdlib from 8.0 before 8.1.1, and hex from 2.4.2 before 2.5.3; hex_core: from 0.14.0 before 0.20.1.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- rebar3
From 3.27.1 · fixed in 3.28.0
- erlang/rebar3
From 23dbdb5d1f87f56902aef296c88a20049cd0c6e4 · fixed in 310e2ec8c7dd3df05d67af2b7fae23f30fc523c4
- hex_core
From 0.14.0 · fixed in 0.20.1
- hexpm/hex_core
From 13bb9fbba418a406af614790b8d5cd458259ee70 · fixed in a2ece683e6e88a3ec95ad20b09aca426e08b372e
- otp
From 29.0 · fixed in 29.1.2
- stdlib
From 8.0 · fixed in 8.1.1
- erlang/otp
From fbf2c7194f6fce4b7b66dc0bcaa4f6b4b85e088f · fixed in 3086307f311b78b38644a7787a3aca6a3f95a9d5
- hex
From 2.4.2 · fixed in 2.5.3
- hexpm/hex
From 5543a1919c709d8eb2b317f62aad76ca1eed375c · fixed in *
- hex_coreHex
From 0.14.0 · fixed in 0.20.1