What is the severity of CVE-2016-10120?

CVE-2016-10120 is considered a high severity vulnerability due to its potential for privilege escalation.

How do I fix CVE-2016-10120?

To fix CVE-2016-10120, update Firejail to a version that implements stricter permissions on the affected mount points.

Who is affected by CVE-2016-10120?

Users of Firejail versions prior to the fix are affected by CVE-2016-10120.

What are the implications of CVE-2016-10120?

The implications of CVE-2016-10120 include the possibility for local users to gain elevated privileges on the system.

Is there a workaround for CVE-2016-10120?

A potential workaround for CVE-2016-10120 is to manually adjust the permissions of the affected directories before applying the update.

Vulnerability/
CVE-2016-10120

high

7.8

CWE

264

13/4/2017

6/8/2024

CVE-2016-10120

First published: Thu Apr 13 2017(Updated: )

Firejail uses 0777 permissions when mounting (1) /dev, (2) /dev/shm, (3) /var/tmp, or (4) /var/lock, which allows local users to gain privileges.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Firejail Project Firejail

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-10120?
CVE-2016-10120 is considered a high severity vulnerability due to its potential for privilege escalation.
How do I fix CVE-2016-10120?
To fix CVE-2016-10120, update Firejail to a version that implements stricter permissions on the affected mount points.
Who is affected by CVE-2016-10120?
Users of Firejail versions prior to the fix are affected by CVE-2016-10120.
What are the implications of CVE-2016-10120?
The implications of CVE-2016-10120 include the possibility for local users to gain elevated privileges on the system.
Is there a workaround for CVE-2016-10120?
A potential workaround for CVE-2016-10120 is to manually adjust the permissions of the affected directories before applying the update.

collector/nvd-index
agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/author
agent/weakness
agent/last-modified-date
agent/severity
agent/description
agent/tags
agent/event
agent/first-publish-date
agent/source
vendor/firejail project
canonical/firejail project firejail

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2016-10120?
CVE-2016-10120 is considered a high severity vulnerability due to its potential for privilege escalation.
How do I fix CVE-2016-10120?
To fix CVE-2016-10120, update Firejail to a version that implements stricter permissions on the affected mount points.
Who is affected by CVE-2016-10120?
Users of Firejail versions prior to the fix are affected by CVE-2016-10120.
What are the implications of CVE-2016-10120?
The implications of CVE-2016-10120 include the possibility for local users to gain elevated privileges on the system.
Is there a workaround for CVE-2016-10120?
A potential workaround for CVE-2016-10120 is to manually adjust the permissions of the affected directories before applying the update.