# CVE-2018-12699: Memory corruption in n/a

> A heap-based buffer overflow in GNU Binutils objdump allows attackers to cause denial of service or potentially execute arbitrary code via crafted files.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** ALSA-2024:9689, CLSA-2024-1732554981, CLSA-2024-1732701075, CLSA-2024-1732701614, DEBIAN-CVE-2018-12699, GHSA-r4rx-vwmc-mj74, RHSA-2024:9689, RLSA-2024:9689, UBUNTU-CVE-2018-12699

## What is CVE-2018-12699?

CVE-2018-12699 is a critical memory corruption vulnerability in Canonical Ubuntu Linux, published on 23 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

finish_stab in stabs.c in GNU Binutils 2.30 allows attackers to cause a denial of service (heap-based buffer overflow) or possibly have unspecified other impact, as demonstrated by an out-of-bounds write of 8 bytes. This can occur during execution of objdump.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2018-12699?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `binutils` | AlmaLinux:8 | All versions | 2.30-125.el8_10 |
| `binutils-devel` | AlmaLinux:8 | All versions | 2.30-125.el8_10 |
| `binutils-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.30-125.el8_10 |
| `binutils-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.30-125.el8_10 |
| `binutils-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.30-125.el8_10 |
| `binutils` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.30-125.el8_10 |
| `binutils-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.30-125.el8_10 |
| `binutils-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.30-125.el8_10 |
| `binutils` | Rocky Linux:8 | All versions | 0:2.30-125.el8_10 |

Products: Canonical Ubuntu Linux, Gnu Binutils.

## How do I fix CVE-2018-12699?

Apply the vendor's patch.

## Is CVE-2018-12699 being exploited?

There is no known exploitation of CVE-2018-12699 in the wild and no public exploit code.

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-12699 and fix it if it is affected.

What it is: CVE-2018-12699 is a critical memory corruption vulnerability in Canonical Ubuntu Linux, published on 23 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-12699 in the wild and no public exploit code.

Affected product: Canonical Ubuntu 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-2018-12699/ (Markdown: https://insights.sbomify.com/CVE-2018-12699/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-12699
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-12699
- OSV: https://osv.dev/vulnerability/CVE-2018-12699

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-12699/
Summaries are generated and may contain mistakes; the official description above is the record.