Confinement escape via malformed AppArmor policy paths
Published Feb 17, 2022 · Updated Aug 3, 2024
Improper path validation in Canonical snapd 2.54.2 and earlier allows local users to escape strict snap confinement. Content-interface and layout declarations accept malformed paths that are embedded as arbitrary AppArmor policy rules in a snap's generated profile. Exploitation requires installing and running a crafted snap locally; the injected rules grant access outside the snap sandbox.
Summary
What happened
Improper path validation in Canonical snapd 2.54.2 and earlier allows local users to escape strict snap confinement. Content-interface and layout declarations accept malformed paths that are embedded as arbitrary AppArmor policy rules in a snap's generated profile. Exploitation requires installing and running a crafted snap locally; the injected rules grant access outside the snap sandbox.
The record
- CVE
- CVE-2021-4120
- Published
- Feb 17, 2022
- Updated
- Aug 3, 2024
- Vendor
- Canonical
- Product
- snapd
- Classifications
- CWE-20, T1611
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 17, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <=2.54.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Malformed snap.yaml AppArmor policy injection proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo