CVE-2017-14178 json
In snapd 2.27 through 2.29.2 the 'snap logs' command could be made to call journalctl without match arguments and therefore allow unprivile…
published 8y ago modified 4mo ago also EUVD-2017-5688
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 0
- none known
Summary
In snapd 2.27 through 2.29.2 the 'snap logs' command could be made to call journalctl without match arguments and therefore allow unprivileged, unauthenticated users to bypass systemd-journald's access restrictions.
Patch / fix
- snapd Debian 14, Debian 13, Debian 12 2.30-1
debian advisories DEBIAN-CVE-2017-14178
- snapd Ubuntu 14.04 LTS 2.29.4.2~14.04
- snapd Ubuntu 16.04 LTS 2.29.4.2
ubuntu advisories UBUNTU-CVE-2017-14178
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-2017-14178 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 FencerExploit prediction
1.76% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- n/a snapd
Classification
- Weakness
-
- CWE-755 Improper Handling of Exceptional Conditions
References
-
github.com
/snapcore/snapd/pull/4194
issue-tracking, third-party-advisory
-
people.canonical.com
/~ubuntu-security/cve/2017/CVE-2017-14178.html
patch, vendor-advisory
-
launchpad.net
/bugs/1730255
issue-tracking, patch
Sources
- CVE List CVE-2017-14178
- NVD CVE-2017-14178
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.