CVE-2017-5940: High severity Firejail Project Firejail vulnerability
Firejail before 0.9.44.6 and 0.9.38.x LTS before 0.9.38.10 LTS does not comprehensively address dotfile cases during its attempt to prevent accessing user files with an euid of zero, which allows local users to conduct sandbox-escape attacks via vectors involving a symlink and the --private option. NOTE: this vulnerability exists because of an incomplete fix for CVE-2017-5180.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
firejailto a version that resolves this vulnerability.Fixed in 0.9.38.10 - Upgrade
Upgrade
firejailto a version that resolves this vulnerability.Fixed in 0.9.44.6
Event History
Frequently Asked Questions
What is the severity of CVE-2017-5940?
CVE-2017-5940 is classified as a high severity vulnerability due to the potential for local users to escape sandbox restrictions.
How do I fix CVE-2017-5940?
To fix CVE-2017-5940, you should upgrade Firejail to version 0.9.44.6 or later, or to 0.9.38.10 LTS or later.
What systems are affected by CVE-2017-5940?
CVE-2017-5940 affects Firejail versions prior to 0.9.44.6 and 0.9.38.10 for the Long Term Support (LTS) versions.
What is the nature of the attack related to CVE-2017-5940?
The attack related to CVE-2017-5940 involves local users exploiting symlink vulnerabilities to bypass sandbox restrictions.
Can CVE-2017-5940 affect user files?
Yes, CVE-2017-5940 can potentially allow local users to access user files by exploiting the sandbox escape flaw.