Ubuntu LinuxOperating system · Canonical
CVE-2022-28658
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedApport argument parsing mishandles filename splitting on older kernels resulting in argument spoofing
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceApport's argument parsing mishandles filename splitting on older Linux kernels, which can lead to argument spoofing. The vulnerability exists in how Apport processes file arguments when parsing command-line inputs, potentially allowing an attacker to inject or manipulate arguments through malformed filenames on systems running older kernel versions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Ubuntu LinuxOperating system
= 18.04= 20.04= 21.10= 22.04< 2.21.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Apport is installedRun `dpkg -l apport` or `which apport` to confirm Apport is present on the systemAffected if Apport is not installed - the system is not vulnerable to this specific flaw
-
Check installed Apport versionRun `apt show apport 2>/dev/null | grep Version` or `dpkg -l apport | grep apport` to obtain the exact version numberAffected if The installed version is lower than 2.21.0 (e.g., 2.20.x or earlier) - the version is vulnerable
-
Confirm Ubuntu versionRun `lsb_release -r` or check `/etc/lsb-release` to identify the Ubuntu releaseAffected if Running Ubuntu 18.04, 20.04, 21.10, or 22.04 with a vulnerable Apport version indicates potential exposure
-
Check kernel versionRun `uname -r` to determine the running Linux kernel versionAffected if The vulnerability affects older Linux kernels - compare your kernel to the timeline of when Ubuntu patches were released
A system is likely affected if Apport is installed with a version below 2.21.0 on a vulnerable Ubuntu release (18.04 through 22.04) running an older kernel version.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.21.0
Update Apport to the latest version when a patch becomes available, as the fix requires correcting the argument parsing logic to properly handle filename splitting across different kernel versions.
Apport 2.21.0 or later (included in Ubuntu 22.04 and backported to 18.04, 20.04, 21.10 via security updates)
- 1. Update the package repository index: sudo apt update
- 2. Upgrade Apport to the fixed version: sudo apt install --upgrade apport
- 3. Verify the installed version is 2.21.0 or later: apport-cli --version OR apt show apport | grep Version
- 4. If the system is running an older Ubuntu version that doesn't have Apport 2.21.0 in its repositories, consider upgrading to a newer Ubuntu LTS release that includes the fixed version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ubuntu Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28658 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-28658 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data