First published: Wed Apr 24 2019(Updated: )
snap-confine in snapd before 2.38 incorrectly set the ownership of a snap application to the uid and gid of the first calling user. Consequently, that user had unintended access to a private /tmp directory.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Canonical snapd | <2.38 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2019-11502 is high with a severity value of 7.5.
The version of snapd before 2.38 is affected by CVE-2019-11502.
CVE-2019-11502 in snap-confine incorrectly sets the ownership of a snap application, allowing unintended access to a private /tmp directory.
Update snapd to version 2.38 or above to fix CVE-2019-11502.
You can find more information about CVE-2019-11502 at the following references: [1](http://www.openwall.com/lists/oss-security/2019/04/25/7) [2](https://github.com/snapcore/snapd/commit/bdbfeebef03245176ae0dc323392bb0522a339b1) [3](https://www.openwall.com/lists/oss-security/2019/04/18/4)