CVE-2017-1000383: Infoleak
First published: Tue Oct 31 2017(Updated: )
GNU Emacs version 25.3.1 (and other versions most likely) ignores umask when creating a backup save file ("[ORIGINAL_FILENAME]~") resulting in files that may be world readable or otherwise accessible in ways not intended by the user running the emacs binary.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GNU Emacs | <=25.3.0 |
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-2017-1000383?
CVE-2017-1000383 is considered a medium severity vulnerability due to the potential exposure of sensitive data.
How do I fix CVE-2017-1000383?
Updating GNU Emacs to version 25.3.1 or later will resolve the issue as it addresses the umask ignoring behavior.
Which versions of GNU Emacs are affected by CVE-2017-1000383?
GNU Emacs versions prior to 25.3.1, including version 25.3.0, are affected by CVE-2017-1000383.
What does CVE-2017-1000383 impact?
CVE-2017-1000383 impacts the backup save files created by GNU Emacs, which may become world-readable.
Can CVE-2017-1000383 lead to data exposure?
Yes, CVE-2017-1000383 can lead to unintended data exposure, allowing unauthorized access to backup save files.
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/last-modified-date
- agent/weakness
- agent/author
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/gnu
- canonical/gnu emacs
- version/gnu emacs/25.3.0