CVE-1999-1221: Low severity digital unix vulnerability
dxchpwd in Digital Unix (OSF/1) 3.x allows local users to modify arbitrary files via a symlink attack on the dxchpwd.log file.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Remove
Remove
dxchpwdfrom your environment.If dxchpwd is not required on the system, uninstall or remove the dxchpwd binary to eliminate the vulnerable component.
- Configuration
Ensure dxchpwd.log is created with secure ownership and permissions so local users cannot replace it with a symlink. Set the file owner to root and remove write permissions for non-privileged accounts; ensure the log file is created by the privileged process before dropping privileges.
dxchpwd (Digital Unix / OSF/1 3.x) dxchpwd.log ownership/permissions = owned by root and not writable by unprivileged users - Compensating control
Restrict unprivileged local user ability to create or modify files/symlinks in the directory where dxchpwd.log is stored (e.g., adjust directory permissions or limit accounts) to prevent symlink attacks against dxchpwd.log.
Event History
Frequently Asked Questions
What is the severity of CVE-1999-1221?
CVE-1999-1221 is classified as a high-severity vulnerability due to its potential for local users to modify arbitrary files.
How do I fix CVE-1999-1221?
To mitigate CVE-1999-1221, ensure that appropriate permissions are set on the dxchpwd.log file to prevent symlink attacks.
Who is affected by CVE-1999-1221?
CVE-1999-1221 affects local users of Digital Unix (OSF/1) version 3.x.
What kind of attack is CVE-1999-1221 exploiting?
CVE-1999-1221 exploits a symlink attack that allows local users to alter log files.
Is there any workaround for CVE-1999-1221?
A possible workaround for CVE-1999-1221 is to regularly monitor file permissions and logs to detect unauthorized changes.