CVE-2018-17955: Static tempfile name allows overwriting of arbitrary files
First published: Fri Mar 15 2019(Updated: )
In yast2-multipath before version 4.1.1 a static temporary filename allows local attackers to overwrite files on systems without symlink protection
Credit: meissner@suse.de
| Affected Software | Affected Version | How to fix |
|---|---|---|
| openSUSE YaST | <4.1.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2018-17955?
CVE-2018-17955 is considered a medium severity vulnerability due to its potential for local file overwrite attacks.
How do I fix CVE-2018-17955?
To fix CVE-2018-17955, update yast2-multipath to version 4.1.1 or later.
Who is affected by CVE-2018-17955?
Users of yast2-multipath versions prior to 4.1.1 on openSUSE systems are at risk from CVE-2018-17955.
What type of attack does CVE-2018-17955 allow?
CVE-2018-17955 allows local attackers to overwrite files due to the use of a static temporary filename.
Is symlink protection related to CVE-2018-17955?
Yes, CVE-2018-17955 affects systems that do not have symlink protection enabled.
- agent/weakness
- agent/type
- agent/softwarecombine
- agent/title
- agent/severity
- agent/author
- agent/remedy
- agent/references
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/opensuse
- canonical/opensuse yast