Aptdaemon error messages disclosed file existence to unprivileged users via dbus properties

published 2020-12-09 5y ago modified 2026-06-17 4mo ago also EUVD-2020-8094

cvss: 3.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 27%
public exploits: 0; none known

The aptdaemon DBus interface disclosed file existence disclosure by setting Terminal/DebconfSocket properties, aka GHSL-2020-192 and GHSL-2020-196. This affected versions prior to 1.1.1+bzr982-0ubuntu34.1, 1.1.1+bzr982-0ubuntu32.3, 1.1.1+bzr982-0ubuntu19.5, 1.1.1+bzr982-0ubuntu14.5.

Patch / fix

fixed in 1 distros 1 links 1

Canonical aptdaemon 1.1.1+bzr982-0ubuntu14.5, 1.1.1+bzr982-0ubuntu19.5, 1.1.1+bzr982-0ubuntu32.3, 1.1.1+bzr982-0ubuntu34.1

aptdaemon Ubuntu 16.04 LTS 1.1.1+bzr982-0ubuntu14.5
aptdaemon Ubuntu 18.04 LTS 1.1.1+bzr982-0ubuntu19.5
aptdaemon Ubuntu 20.04 LTS 1.1.1+bzr982-0ubuntu32.3

ubuntu advisories UBUNTU-CVE-2020-16128

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

usn.ubuntu.com/usn/usn-4664-1 advisory

Is CVE-2020-16128 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 Fencer

Exploit prediction

0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	3.8	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
NVD	3.1	3.8	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
NVD	2.0	2.1	AV:L/AC:L/Au:N/C:P/I:N/A:N

Affected products

Canonical aptdaemon

Classification

Weakness

CWE-209 Generation of Error Message Containing Sensitive Information

References

usn.ubuntu.com /usn/usn-4664-1
patch, third-party-advisory
bugs.launchpad.net /ubuntu/+source/aptdaemon/+bug/1899513
broken-link

Sources

CVE List CVE-2020-16128
NVD CVE-2020-16128

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.