CVE-1999-0857: Low severity FreeBSD FreeBSD vulnerability
FreeBSD gdc program allows local users to modify files via a symlink attack.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Remove
Remove
FreeBSD gdcfrom your environment.Uninstall the gdc program if it is not required to eliminate the symlink-based local file modification vector.
- Configuration
Restrict access to the gdc binary to administrative/trusted accounts until an official vendor fix is available (for example, remove it from non-privileged users' PATH or adjust filesystem permissions/ACLs to prevent execution by regular users).
FreeBSD gdc program access control = restricted to administrative/trusted users - Compensating control
Apply host-level controls to limit exploitation by local users until patched — e.g., restrict which accounts can run gdc via sudoers or ACLs, isolate untrusted users (containers/ jails), and monitor alerts/logs for unexpected file modifications.
Event History
Frequently Asked Questions
What is the severity of CVE-1999-0857?
CVE-1999-0857 is considered a moderate severity vulnerability due to its potential to allow unauthorized file modifications.
How do I fix CVE-1999-0857?
To fix CVE-1999-0857, it is recommended to update to a version of FreeBSD that is not vulnerable to this symlink attack.
Who is affected by CVE-1999-0857?
CVE-1999-0857 affects local users on FreeBSD version 3.3, enabling them to exploit symlink vulnerabilities.
What is a symlink attack in the context of CVE-1999-0857?
A symlink attack, as related to CVE-1999-0857, involves manipulating symbolic links to redirect file operations and modify sensitive files.
Can CVE-1999-0857 be exploited remotely?
CVE-1999-0857 requires local access to the system, so it cannot be exploited remotely.