SnapdApplication · Canonical
CVE-2022-3328
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 · uneditedRace condition in snap-confine's must_mkdir_and_open_with_perms()
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 confidenceA race condition exists in snap-confine's must_mkdir_and_open_with_perms() function. This function handles directory creation with specific permissions during snap package execution. The race condition likely involves a time-of-check to time-of-use (TOCTOU) issue where an attacker could potentially manipulate filesystem state between the permission check and the actual file/directory operation, possibly enabling privilege escalation or confinement bypass.
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
SnapdApplication
< 2.61.1
Ubuntu LinuxOperating system
= 16.04= 18.04= 20.04= 22.04= 22.10CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/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 snapd is installedRun `systemctl status snapd.service` or check if /snap/bin directory existsAffected if snapd is not installed - the vulnerability does not apply
-
Check Ubuntu release versionRun `lsb_release -r` or check /etc/lsb-releaseAffected if Version is 16.04, 18.04, 20.04, 22.04, or 22.10 - these are in the affected range
-
Determine snapd versionRun `snap --version` or `snapd --version` to get the installed snapd version numberAffected if Version is less than 2.61.1 - the version is vulnerable
-
Locate snap-confine binaryCheck for /usr/lib/snapd/snap-confine or /snap/bin/snap-confineAffected if The binary exists and snap packages are used, the must_mkdir_and_open_with_perms() function is in use
-
Check for active snap processesRun `ps aux | grep snap` to see if any snap applications are currently executingAffected if Snap processes are running, the vulnerable code path could be triggered
The environment is affected if snapd is installed on an affected Ubuntu version (16.04-22.10) with snapd version less than 2.61.1 and snap-confine is in use.
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.61.1
Apply the vendor patch for snap-confine when available. If a patch is not immediately available, consider restricting snap package installations or running snaps in isolated environments until the fix can be deployed.
snapd >= 2.61.1
- Check the current snapd version by running: snapd --version or snap version
- Update snapd to the fixed version by running: sudo snap refresh snapd
- Verify the update was successful by checking: snapd --version (should be >= 2.61.1)
- If using classic confinement snaps, ensure they are restarted after the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Snapd
Scoped from the published advisory
- Consultation2.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3328 — 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-3328 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