What is the severity of CVE-2017-18188?

CVE-2017-18188 is considered a moderate severity vulnerability as it allows local users to potentially take ownership of arbitrary files.

How do I fix CVE-2017-18188?

To mitigate CVE-2017-18188, ensure that the fs.protected_hardlinks sysctl setting is enabled.

Which versions of OpenRC opentmpfiles are affected by CVE-2017-18188?

CVE-2017-18188 affects OpenRC opentmpfiles versions up to and including 0.1.3.

Can remote users exploit CVE-2017-18188?

No, CVE-2017-18188 can only be exploited by local users with access to the system.

What actions can be taken to secure a system affected by CVE-2017-18188?

In addition to enabling fs.protected_hardlinks, regularly update OpenRC opentmpfiles to ensure any security patches are applied.

Vulnerability/
CVE-2017-18188

medium

5.5

CWE

14/2/2018

16/9/2024

CVE-2017-18188

First published: Wed Feb 14 2018(Updated: )

OpenRC opentmpfiles through 0.1.3, when the fs.protected_hardlinks sysctl is turned off, allows local users to obtain ownership of arbitrary files by creating a hard link inside a directory on which "chown -R" will be run.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Openr Opentmpfiles	<=0.1.3

Never miss a vulnerability like this again

Reference Links

https://github.com/OpenRC/opentmpfiles/issues/3

Frequently Asked Questions

What is the severity of CVE-2017-18188?
CVE-2017-18188 is considered a moderate severity vulnerability as it allows local users to potentially take ownership of arbitrary files.
How do I fix CVE-2017-18188?
To mitigate CVE-2017-18188, ensure that the fs.protected_hardlinks sysctl setting is enabled.
Which versions of OpenRC opentmpfiles are affected by CVE-2017-18188?
CVE-2017-18188 affects OpenRC opentmpfiles versions up to and including 0.1.3.
Can remote users exploit CVE-2017-18188?
No, CVE-2017-18188 can only be exploited by local users with access to the system.
What actions can be taken to secure a system affected by CVE-2017-18188?
In addition to enabling fs.protected_hardlinks, regularly update OpenRC opentmpfiles to ensure any security patches are applied.

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

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-2017-18188?
CVE-2017-18188 is considered a moderate severity vulnerability as it allows local users to potentially take ownership of arbitrary files.
How do I fix CVE-2017-18188?
To mitigate CVE-2017-18188, ensure that the fs.protected_hardlinks sysctl setting is enabled.
Which versions of OpenRC opentmpfiles are affected by CVE-2017-18188?
CVE-2017-18188 affects OpenRC opentmpfiles versions up to and including 0.1.3.
Can remote users exploit CVE-2017-18188?
No, CVE-2017-18188 can only be exploited by local users with access to the system.
What actions can be taken to secure a system affected by CVE-2017-18188?
In addition to enabling fs.protected_hardlinks, regularly update OpenRC opentmpfiles to ensure any security patches are applied.