Ubuntu LinuxOperating system · Canonical
CVE-2022-28657
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 does not disable python crash handler before entering chroot
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/Debian crash handler, fails to disable the Python crash handler before entering a chroot environment. This allows the crash handler to potentially execute within the chroot context, which could be exploited for local privilege escalation or escape from chroot isolation.
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
- 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 apport' or 'which apport' to confirm the Apport package is present on the systemAffected if Apport is not installed on the system (not vulnerable if absent)
-
Retrieve installed Apport versionRun 'apport --version' or 'dpkg -s apport' to obtain the exact version number of the installed Apport packageAffected if Unable to determine version (Apport may be installed but not functional)
-
Compare version against vulnerable rangeCheck if the installed version is less than 2.21.0. For Ubuntu versions: 18.04, 20.04, 21.10, and 22.04 ship with Apport versions that predate the fixAffected if Installed version is less than 2.21.0 (e.g., 2.20.x or earlier series)
-
Confirm Apport crash handler capability is enabledApport is typically enabled by default on Ubuntu desktop installations. Check '/etc/default/apport' or verify the apport service is active via 'systemctl status apport'Affected if Apport is enabled and running as a service, making the vulnerable code path reachable
The system is affected if Apport is installed with version < 2.21.0 and the Apport crash handling service is enabled, allowing the Python crash handler to execute within chroot contexts.
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
Modify Apport to explicitly disable or reset the Python crash handler (sys.excepthook) before executing chroot operations, ensuring no handler code runs in the untrusted chroot context.
Apport >= 2.21.0 (or the latest version available in your Ubuntu version's repository)
- Run 'sudo apt update' to refresh package lists
- Run 'sudo apt install --upgrade apport' to upgrade Apport to the latest available version
- Verify the upgrade was successful by running ' apport-cli --version' or 'dpkg -l | grep apport'
- Ensure the installed version is >= 2.21.0 which contains the fix for CVE-2022-28657
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ubuntu Linux
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28657 — 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-28657 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