CVE-1999-0371: Low severity university of kansas lynx vulnerability
Lynx allows a local user to overwrite sensitive files through /tmp symlinks.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
If Lynx is installed with elevated privileges (setuid/root), remove the setuid bit or configure Lynx to drop privileges so it does not run with higher privileges that would allow a local user to overwrite sensitive files via /tmp symlinks.
Lynx setuid_enabled = false - Compensating control
Prevent symlink-based attacks in /tmp, e.g. mount /tmp with the nosymfollow option or otherwise configure the filesystem to avoid following user-created symlinks in /tmp.
- Operational
Scan /tmp for user-created symlinks that point to sensitive files and remove them; verify integrity of any sensitive files that may have been overwritten and restore from trusted backups; audit and restrict local accounts that could create such symlinks.
Event History
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.