elfutils: The libcpu component which is used by libasm of elfutils version 0.177 (git 47780c9e), suffers from denial-of-service...
CVE-2020-21047 is fixed in 4 products on 1 platform, first by elfutils 0.170-0.4ubuntu0.1+esm1, released August 22, 2023. It is not reported as exploited. Patch Radar priority: Routine.
The libcpu component which is used by libasm of elfutils version 0.177 (git 47780c9e), suffers from denial-of-service vulnerability caused by application crashes due to out-of-bounds write (CWE-787), off-by-one error (CWE-193) and reachable assertion (CWE-617); to exploit the vulnerability, the attackers need to craft certain ELF files which bypass the missing bound checks.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| elfutils · Debian 12.15 (bookworm) | 0.180-1 | DEBIAN-CVE-2020-21047 | Aug 22, 2023 |
| elfutils · Debian 13.5 (trixie) | 0.180-1 | DEBIAN-CVE-2020-21047 | Aug 22, 2023 |
| elfutils · Debian 14 | 0.180-1 | DEBIAN-CVE-2020-21047 | Aug 22, 2023 |
| elfutils · Ubuntu 18.04.6 LTS (bionic) | 0.170-0.4ubuntu0.1+esm1 | elfutils 0.170-0.4ubuntu0.1+esm1 | Aug 22, 2023 |
| elfutils · Ubuntu 20.04 LTS (focal) | 0.176-1.1ubuntu0.1 | elfutils 0.176-1.1ubuntu0.1 | Aug 22, 2023 |
| libasm1 · Ubuntu 18.04.6 LTS (bionic) | 0.170-0.4ubuntu0.1+esm1 | libasm1 0.170-0.4ubuntu0.1+esm1 | Aug 22, 2023 |
| libasm1 · Ubuntu 20.04 LTS (focal) | 0.176-1.1ubuntu0.1 | libasm1 0.176-1.1ubuntu0.1 | Aug 22, 2023 |
| libdw1 · Ubuntu 18.04.6 LTS (bionic) | 0.170-0.4ubuntu0.1+esm1 | libdw1 0.170-0.4ubuntu0.1+esm1 | Aug 22, 2023 |
| libdw1 · Ubuntu 20.04 LTS (focal) | 0.176-1.1ubuntu0.1 | libdw1 0.176-1.1ubuntu0.1 | Aug 22, 2023 |
| libelf1 · Ubuntu 18.04.6 LTS (bionic) | 0.170-0.4ubuntu0.1+esm1 | libelf1 0.170-0.4ubuntu0.1+esm1 | Aug 22, 2023 |
| libelf1 · Ubuntu 20.04 LTS (focal) | 0.176-1.1ubuntu0.1 | libelf1 0.176-1.1ubuntu0.1 | Aug 22, 2023 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.