CVE-2015-3171: Infoleak
It was reported that sosreport creates output files with world-readable permissions:
-rw-r--r--. 1 root root 7331624 May 4 08:55 sosreport-localhost.localdomain-20150504084328.tar.xz -rw-r--r--. 1 root root 33 May 4 08:55 sosreport-localhost.localdomain-20150504084328.tar.xz.md5
The archive may consists of files originally only accessible by the root user. However, after extracting the archive, all of the files are readable by regular users with access to /var/tmp/.
Acknowledgements:
Red Hat would like to thank Grant Murphy for reporting this issue.
Other sources
sosreport 3.2 uses weak permissions for generated sosreport archives, which allows local users with access to /var/tmp/ to obtain sensitive information by reading the contents of the archive.
— MITRE
sosreport 3.2 uses weak permissions for generated sosreport archives, which allows local users with access to /var/tmp/ to obtain sensitive information by reading the contents of the archive.
— GitHub
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2015-3171?
CVE-2015-3171 is considered to have a medium severity due to the potential exposure of sensitive information.
How do I fix CVE-2015-3171?
To fix CVE-2015-3171, upgrade to sosreport version 3.3 or later.
What does CVE-2015-3171 affect?
CVE-2015-3171 affects the sosreport tool, specifically versions below 3.3.
What are the potential risks of CVE-2015-3171?
The main risk associated with CVE-2015-3171 is that the output files generated may contain sensitive data that is publicly readable.
Is CVE-2015-3171 exploitable remotely?
CVE-2015-3171 is not typically considered remotely exploitable; it primarily pertains to local file permission issues.