ApportApplication · Canonical
CVE-2022-1242
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 can be tricked into connecting to arbitrary sockets as the root user
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, the Ubuntu crash reporting tool, contains a vulnerability where it can be manipulated into connecting to arbitrary sockets when operating with root privileges. This allows a local attacker to potentially redirect Apport's socket connections to attacker-controlled endpoints, potentially leading to privilege escalation or arbitrary code execution as root.
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
ApportApplication
< 2.21.0
Ubuntu LinuxOperating system
= 18.04= 20.04= 21.10= 22.04CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 | grep apport or which apportAffected if Apport package is present on the system
-
Check installed Apport versionRun: apt-cache policy apport and compare the installed version number to 2.21.0Affected if Installed version is lower than 2.21.0
-
Confirm Ubuntu versionRun: lsb_release -r or check /etc/lsb-releaseAffected if Running Ubuntu 18.04, 20.04, 21.10, or 22.04 with vulnerable Apport version
-
Check Apport service statusRun: systemctl status apport or check if /var/crash is writable by user processes that could manipulate socket connectionsAffected if Apport daemon is running with root privileges and has ability to connect to arbitrary sockets
A system is affected if it runs Ubuntu 18.04, 20.04, 21.10, or 22.04 with Apport version lower than 2.21.0 and the Apport service runs with root privileges.
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
Restrict Apport's ability to connect to arbitrary sockets by implementing socket allowlisting or removing unnecessary socket connection capabilities from Apport's execution context. Consider running Apport with reduced privileges or in a sandboxed environment where socket connections are explicitly controlled.
Apport 2.21.0 or later
- Update the system package lists: sudo apt-get update
- Upgrade Apport to the fixed version: sudo apt-get install --upgrade apport
- Verify the installed Apport version is 2.21.0 or later: apport-cli --version or dpkg -s apport | grep Version
- Restart any Apport-related services if necessary: sudo systemctl restart apport
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Apport
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1242 — 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-1242 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