CVE-1999-0371
First published: Thu Feb 11 1999(Updated: )
Lynx allows a local user to overwrite sensitive files through /tmp symlinks.
Credit: cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Lynx | <=2.7.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.
Frequently Asked Questions
What is the severity of CVE-1999-0371?
CVE-1999-0371 is considered a medium severity vulnerability due to the potential for local users to overwrite sensitive files.
Which versions of Lynx are affected by CVE-1999-0371?
CVE-1999-0371 affects Lynx versions up to and including 2.7.1.
How do I fix CVE-1999-0371?
To fix CVE-1999-0371, upgrade Lynx to a version later than 2.7.1 where the issue is resolved.
Can I mitigate CVE-1999-0371 without updating my software?
Yes, you can mitigate CVE-1999-0371 by restricting permissions on the /tmp directory to prevent symlink manipulation.
What type of attack is possible with CVE-1999-0371?
CVE-1999-0371 can lead to local file overwrite attacks, allowing unauthorized changes to sensitive files on the system.
- agent/type
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/references
- agent/weakness
- agent/description
- agent/last-modified-date
- agent/author
- agent/softwarecombine
- agent/event
- agent/source
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/nvd-historical
- vendor/university of kansas
- product/lynx
- canonical/university of kansas lynx
- collector/nvd-index
- canonical/lynx
- version/lynx/2.7.1