CVE-2018-18700 json
An issue was discovered in cp-demangle.c in GNU libiberty, as distributed in GNU Binutils 2.31.
published 8y ago modified 25d ago also EUVD-2018-10416
- cvss
- 5.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
An issue was discovered in cp-demangle.c in GNU libiberty, as distributed in GNU Binutils 2.31. There is a stack consumption vulnerability resulting from infinite recursion in the functions d_name(), d_encoding(), and d_local_name() in cp-demangle.c. Remote attackers could leverage this vulnerability to cause a denial-of-service via an ELF file, as demonstrated by nm.
Patch / fix
- binutils Debian 14, Debian 13, Debian 12 2.32.51.20190707-1
debian advisories DEBIAN-CVE-2018-18700
- binutils Ubuntu 18.04 LTS 2.30-21ubuntu1~18.04.3
- libiberty Ubuntu 16.04 LTS 20160215-1ubuntu0.3
- libiberty Ubuntu 18.04 LTS 20170913-1ubuntu0.1
- binutils Ubuntu Pro 16.04 LTS 2.26.1-1ubuntu1~16.04.8+esm1
ubuntu advisories UBUNTU-CVE-2018-18700
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Is CVE-2018-18700 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2018-18700 updated cvss 4.3
binutils: Recursive Stack Overflow within function d_name, d_encoding, and d_local_name in cp-demangle.c
-
Red Hat Enterprise Linux 5 binutils, binutils220 Red Hat Enterprise Linux 6 binutils Red Hat Enterprise Linux 7 binutilsaffected: no fix planned “Will not fix”
-
Red Hat Enterprise Linux 8 binutils, mingw-binutils, mingw32-binutils, mingw64-binutils, mingw-binutils-genericaffected: no fix available, no fix planned “Will not fix”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 25d ago
Exploit prediction
1.69% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- gcc.gnu.org https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87681 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.5 | CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-835 Loop with Unreachable Exit Condition
References
-
gcc.gnu.org
/bugzilla/show_bug.cgi?id=87681
exploit, issue-tracking, vendor-advisory
-
usn.ubuntu.com
/4326-1/
vendor-advisory
-
usn.ubuntu.com
/4336-1/
vendor-advisory
Sources
- CVE List CVE-2018-18700
- NVD CVE-2018-18700
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.