CVE-2020-16121

What it actually does

Unprivileged local callers receive verbose PackageKit error responses that disclose file existence and MIME type information otherwise inaccessible to the caller.

Why it matters to the business

Attackers on the same system can silently map sensitive file locations and types, aiding reconnaissance for follow-on attacks; the issue affects widely deployed Linux distributions with PackageKit but carries low exploit probability.

How an attack unfolds

A local attacker invokes PackageKit operations that trigger controlled errors, parses the returned messages to learn about otherwise hidden files, and uses the gathered intelligence to plan subsequent local attacks.

How to fix it

Update PackageKit to a version that suppresses verbose error details for unprivileged callers; apply all available distribution security updates for affected Ubuntu releases.

How to confirm the fix worked

Confirm PackageKit version is newer than the vulnerable releases and test that error messages no longer leak file-presence or MIME-type details to non-root users.

Typical attack path

1. Obtain local unprivileged shell access
2. Invoke PackageKit API or command-line tools to request operations on guessed file paths
3. Inspect detailed error responses for presence and MIME-type leaks
4. Map file system layout and file types for further exploitation

How to detect it

Monitor PackageKit and system logs for repeated or unusual error queries from non-privileged processes; correlate with local user activity around file-system reconnaissance.

What your security team should do

• Patch PackageKit on all Ubuntu systems within standard maintenance windows
• Review local PackageKit logs for anomalous error-query patterns
• Harden local access controls to reduce unprivileged attacker opportunities