# CVE-2014-0172: Integer overflow in n/a > Remote attackers can cause denial of service or execute arbitrary code via a malformed ELF file processed by the libdw library. - **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 11 Apr 2014 - **Updated:** 6 Aug 2024 - **Also known as:** DEBIAN-CVE-2014-0172, GHSA-q6c9-79p5-7pgm, MGASA-2014-0177, RHEA-2015:0369, UBUNTU-CVE-2014-0172, USN-2188-1 ## What is CVE-2014-0172? CVE-2014-0172 is a medium-severity vulnerability in n/a, published on 11 Apr 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Integer overflow in the check_section function in dwarf_begin_elf.c in the libdw library, as used in elfutils 0.153 and possibly through 0.158 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a malformed compressed debug section in an ELF file, which triggers a heap-based buffer overflow. Weakness: CWE-189 ## Which versions are affected by CVE-2014-0172? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `elfutils` | Red Hat:enterprise_linux:7::client | All versions | 0:0.160-1.el7 | | `elfutils-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:0.160-1.el7 | | `elfutils-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:0.160-1.el7 | | `elfutils-devel-static` | Red Hat:enterprise_linux:7::client | All versions | 0:0.160-1.el7 | | `elfutils-libelf` | Red Hat:enterprise_linux:7::client | All versions | 0:0.160-1.el7 | | `elfutils-libelf-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:0.160-1.el7 | | `elfutils-libelf-devel-static` | Red Hat:enterprise_linux:7::client | All versions | 0:0.160-1.el7 | | `elfutils-libs` | Red Hat:enterprise_linux:7::client | All versions | 0:0.160-1.el7 | | `elfutils` | Red Hat:enterprise_linux:7::computenode | All versions | 0:0.160-1.el7 | | `elfutils-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:0.160-1.el7 | | `elfutils-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:0.160-1.el7 | | `elfutils-devel-static` | Red Hat:enterprise_linux:7::computenode | All versions | 0:0.160-1.el7 | | `elfutils-libelf` | Red Hat:enterprise_linux:7::computenode | All versions | 0:0.160-1.el7 | | `elfutils-libelf-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:0.160-1.el7 | | `elfutils-libelf-devel-static` | Red Hat:enterprise_linux:7::computenode | All versions | 0:0.160-1.el7 | | `elfutils-libs` | Red Hat:enterprise_linux:7::computenode | All versions | 0:0.160-1.el7 | | `elfutils` | Red Hat:enterprise_linux:7::server | All versions | 0:0.160-1.el7 | | `elfutils-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:0.160-1.el7 | | `elfutils-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:0.160-1.el7 | | `elfutils-devel-static` | Red Hat:enterprise_linux:7::server | All versions | 0:0.160-1.el7 | | `elfutils-libelf` | Red Hat:enterprise_linux:7::server | All versions | 0:0.160-1.el7 | | `elfutils-libelf-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:0.160-1.el7 | | `elfutils-libelf-devel-static` | Red Hat:enterprise_linux:7::server | All versions | 0:0.160-1.el7 | | `elfutils-libs` | Red Hat:enterprise_linux:7::server | All versions | 0:0.160-1.el7 | | `elfutils` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.160-1.el7 | | `elfutils-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.160-1.el7 | | `elfutils-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.160-1.el7 | | `elfutils-devel-static` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.160-1.el7 | | `elfutils-libelf` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.160-1.el7 | | `elfutils-libelf-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.160-1.el7 | | `elfutils-libelf-devel-static` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.160-1.el7 | | `elfutils-libs` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.160-1.el7 | Products: Elfutils Project Elfutils. ## How do I fix CVE-2014-0172? Upgrade to a fixed version. ## Is CVE-2014-0172 being exploited? There is no known exploitation of CVE-2014-0172 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2018-8769](https://insights.sbomify.com/CVE-2018-8769/): Memory corruption in n/a (high 7.8) - [CVE-2019-7148](https://insights.sbomify.com/CVE-2019-7148/): Denial of service in n/a (medium 6.5) - [CVE-2014-9447](https://insights.sbomify.com/CVE-2014-9447/): Path traversal in n/a (medium 6.4) - [CVE-2020-21047](https://insights.sbomify.com/CVE-2020-21047/): Memory corruption in n/a (medium 5.5) - [CVE-2021-33294](https://insights.sbomify.com/CVE-2021-33294/): Denial of service in n/a (medium 5.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2014-0172 and fix it if it is affected. What it is: CVE-2014-0172 is a medium-severity vulnerability in n/a, published on 11 Apr 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2014-0172 in the wild and no public exploit code. Affected product: n/a. 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-2014-0172/ (Markdown: https://insights.sbomify.com/CVE-2014-0172/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2014-0172 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-0172 - OSV: https://osv.dev/vulnerability/CVE-2014-0172 --- From sbomify Insights: https://insights.sbomify.com/CVE-2014-0172/ Summaries are generated and may contain mistakes; the official description above is the record.