CVE-2020-5208 remote code execution vulnerability in ipmitool
High 7.7
Published
Updated
Check this codebase for CVE-2020-5208 and fix it if it is affected.
What it is: CVE-2020-5208 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 5 Feb 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-5208 in the wild and no public exploit code.
Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2020-5208/ (Markdown: https://insights.sbomify.com/CVE-2020-5208/index.md)
Remote attackers can trigger buffer overflows in ipmitool to execute arbitrary code, especially if the tool runs with elevated privileges.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2020-5208?
CVE-2020-5208 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 5 Feb 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
It's been found that multiple functions in ipmitool before 1.8.19 neglect proper checking of the data received from a remote LAN party, which may lead to buffer overflows and potentially to remote code execution on the ipmitool side. This is especially dangerous if ipmitool is run as a privileged user. This problem is fixed in version 1.8.19.
Weakness: CWE-120
Which versions are affected by CVE-2020-5208?
It affects 4 products.
Linux distribution packages (40)
ipmitool Red Hat:enterprise_linux:6::client | All versions | 0:1.8.15-3.el6_10 |
ipmitool-debuginfo Red Hat:enterprise_linux:6::client | All versions | 0:1.8.15-3.el6_10 |
ipmitool Red Hat:enterprise_linux:6::computenode | All versions | 0:1.8.15-3.el6_10 |
ipmitool-debuginfo Red Hat:enterprise_linux:6::computenode | All versions | 0:1.8.15-3.el6_10 |
ipmitool Red Hat:enterprise_linux:6::server | All versions | 0:1.8.15-3.el6_10 |
ipmitool-debuginfo Red Hat:enterprise_linux:6::server | All versions | 0:1.8.15-3.el6_10 |
ipmitool Red Hat:enterprise_linux:6::workstation | All versions | 0:1.8.15-3.el6_10 |
ipmitool-debuginfo Red Hat:enterprise_linux:6::workstation | All versions | 0:1.8.15-3.el6_10 |
bmc-snmp-proxy Red Hat:enterprise_linux:7::computenode | All versions | 0:1.8.18-9.el7_7 |
exchange-bmc-os-info Red Hat:enterprise_linux:7::computenode | All versions | 0:1.8.18-9.el7_7 |
ipmitool Red Hat:enterprise_linux:7::computenode | All versions | 0:1.8.18-9.el7_7 |
ipmitool-debuginfo Red Hat:enterprise_linux:7::computenode | All versions | 0:1.8.18-9.el7_7 |
bmc-snmp-proxy Red Hat:enterprise_linux:7::server | All versions | 0:1.8.18-9.el7_7 |
exchange-bmc-os-info Red Hat:enterprise_linux:7::server | All versions | 0:1.8.18-9.el7_7 |
ipmitool Red Hat:enterprise_linux:7::server | All versions | 0:1.8.18-9.el7_7 |
ipmitool-debuginfo Red Hat:enterprise_linux:7::server | All versions | 0:1.8.18-9.el7_7 |
bmc-snmp-proxy Red Hat:enterprise_linux:7::workstation | All versions | 0:1.8.18-9.el7_7 |
exchange-bmc-os-info Red Hat:enterprise_linux:7::workstation | All versions | 0:1.8.18-9.el7_7 |
ipmitool Red Hat:enterprise_linux:7::workstation | All versions | 0:1.8.18-9.el7_7 |
ipmitool-debuginfo Red Hat:enterprise_linux:7::workstation | All versions | 0:1.8.18-9.el7_7 |
exchange-bmc-os-info Red Hat:enterprise_linux:8::appstream | All versions | 0:1.8.18-12.el8_1 |
ipmievd Red Hat:enterprise_linux:8::appstream | All versions | 0:1.8.18-12.el8_1 |
ipmievd-debuginfo Red Hat:enterprise_linux:8::appstream | All versions | 0:1.8.18-12.el8_1 |
ipmitool Red Hat:enterprise_linux:8::appstream | All versions | 0:1.8.18-12.el8_1 |
ipmitool-debuginfo Red Hat:enterprise_linux:8::appstream | All versions | 0:1.8.18-12.el8_1 |
ipmitool-debugsource Red Hat:enterprise_linux:8::appstream | All versions | 0:1.8.18-12.el8_1 |
bmc-snmp-proxy Red Hat:rhel_aus:7.2::server | All versions | 0:1.8.13-10.el7_2 |
exchange-bmc-os-info Red Hat:rhel_aus:7.2::server | All versions | 0:1.8.13-10.el7_2 |
ipmitool Red Hat:rhel_aus:7.2::server | All versions | 0:1.8.13-10.el7_2 |
ipmitool-debuginfo Red Hat:rhel_aus:7.2::server | All versions | 0:1.8.13-10.el7_2 |
bmc-snmp-proxy Red Hat:rhel_aus:7.3::server | All versions | 0:1.8.15-8.el7_3 |
exchange-bmc-os-info Red Hat:rhel_aus:7.3::server | All versions | 0:1.8.15-8.el7_3 |
ipmitool Red Hat:rhel_aus:7.3::server | All versions | 0:1.8.15-8.el7_3 |
ipmitool-debuginfo Red Hat:rhel_aus:7.3::server | All versions | 0:1.8.15-8.el7_3 |
bmc-snmp-proxy Red Hat:rhel_aus:7.4::server | All versions | 0:1.8.18-6.el7_4 |
exchange-bmc-os-info Red Hat:rhel_aus:7.4::server | All versions | 0:1.8.18-6.el7_4 |
ipmitool Red Hat:rhel_aus:7.4::server | All versions | 0:1.8.18-6.el7_4 |
ipmitool-debuginfo Red Hat:rhel_aus:7.4::server | All versions | 0:1.8.18-6.el7_4 |
bmc-snmp-proxy Red Hat:rhel_e4s:7.3::server | All versions | 0:1.8.15-8.el7_3 |
exchange-bmc-os-info Red Hat:rhel_e4s:7.3::server | All versions | 0:1.8.15-8.el7_3 |
Products include Debian Debian Linux, Fedoraproject Fedora, Ipmitool Project Ipmitool, Opensuse Leap.
How do I fix CVE-2020-5208?
Upgrade to a fixed version.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2020-5208 being exploited?
There is no known exploitation of CVE-2020-5208 in the wild and no public exploit code.
Other vulnerabilities in Debian Debian Linux
Sources
Also known as AZL-6489, DEBIAN-CVE-2020-5208, DLA-2098-1, DLA-2699-1, GHSA-g659-9qxw-p7cp, MGASA-2020-0097 and 18 more.