CVE-2017-14178: In snapd 2.27 through 2.29.2 the 'snap logs' command could be made to call journalctl without match arguments

This month

HIGH 7.5REMOTEUPGRADE

CVE-2017-14178 is a high-severity flaw (CVSS 7.5) affecting snapd. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.8% (top 22%)
CISA exploited list	No
Weakness	CWE-755
Published	2018-02-02
Last modified	2026-06-17

Publisher (CNA): Canonical Ltd. · Vendor: snapcraft

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-02-02 14:29 UTCPublished CVE record published
2026-06-17 01:05 UTCUpdated Record last modified

snapcraft snapd UPGRADE

Affected: >= 2.27 and <= 2.29.2

Fixed in: newer than 2.29.2

Safe to downgrade to: a release before 2.27

1. Check installed version

apt-cache policy snapd || rpm -q snapd || snapd --version

2. UPGRADE to newer than 2.29.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade snapd

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade snapd

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.27 (Debian / Ubuntu)

apt-cache madison snapd sudo apt install snapd=<VERSION_BEFORE_2.27> sudo apt-mark hold snapd

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list snapd sudo dnf downgrade snapd-<VERSION_BEFORE_2.27> sudo dnf versionlock add snapd

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-14178?

snapd: upgrade to newer than 2.29.2. Exact commands for each OS are on this page.

Is CVE-2017-14178 being exploited?

CVE-2017-14178 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-14178 affect?

CVE-2017-14178 affects snapd. Severity is high (CVSS 7.5). 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.

How urgent is CVE-2017-14178?

Priority 51/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2024-5138 HIGH 8.1 UPGRADE The snapctl component within snapd allows a confined snap to interact with the snapd daemon to take certain pr
CVE-2024-29069 MEDIUM 4.8 UPGRADE In snapd versions prior to 2.62, snapd failed to properly check the destination of symbolic links when extract
CVE-2024-29068 MEDIUM 5.8 UPGRADE In snapd versions prior to 2.62, snapd failed to properly check the file type when extracting a snap
CVE-2024-1724 MEDIUM 6.3 UPGRADE In snapd versions prior to 2.62, when using AppArmor for enforcement of sandbox permissions, snapd failed to
CVE-2023-1523 CRITICAL 10.0 UPGRADE MITIGATE Using the TIOCLINUX ioctl request, a malicious snap could inject contents into the input of the controlling te

References

← Back to latest CVEs