CVE-2017-14177 json
Apport through 2.20.7 does not properly handle core dumps from setuid binaries allowing local users to create certain files as root which a…
published 2018-02-02 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-5687
- cvss
- 7.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 33%
- public exploits
- 0
- none known
Summary
Apport through 2.20.7 does not properly handle core dumps from setuid binaries allowing local users to create certain files as root which an attacker could leverage to perform a denial of service via resource exhaustion or possibly gain root privileges. NOTE: this vulnerability exists because of an incomplete fix for CVE-2015-1324.
Patch / fix
- apport Ubuntu 14.04 LTS 2.14.1-0ubuntu3.27
- apport Ubuntu 16.04 LTS 2.20.1-0ubuntu2.12
ubuntu advisories UBUNTU-CVE-2017-14177
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
Exploit prediction
0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.8 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Affected products
- n/a Apport
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
-
usn.ubuntu.com
/usn/usn-3480-1
vendor-advisory, third-party-advisory
-
people.canonical.com
/~ubuntu-security/cve/?cve=CVE-2017-14177
third-party-advisory
-
bazaar.launchpad.net
/~apport-hackers/apport/trunk/revision/3171
issue-tracking, third-party-advisory
-
launchpad.net
/bugs/1726372
issue-tracking, third-party-advisory
Sources
- CVE List CVE-2017-14177
- NVD CVE-2017-14177
Fencer Vulns 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.