Quick answers
- Is CVE-1999-1221 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-1999-1221 being exploited in the wild.
- How severe is CVE-1999-1221?
- Low severity, with a CVSS score of 2.1, published 17 November 1996.
- Which products and versions are affected?
- Digital Equipment Corporation Digital Unix 3.x.
- Is there a fix for CVE-1999-1221?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-1999-1221 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-1999-1221?
- Check whether you run Digital Equipment Corporation Digital Unix at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The dxchpwd utility, which is part of the C2 security package and typically installed setuid root, creates a log file at /tmp/dxchpwd.log. Because the application does not securely check for the existence of this file before writing to it, a local attacker can create a symbolic link from /tmp/dxchpwd.log to any target file on the system. When dxchpwd is executed, it follows the symlink and writes log data to the target path with root privileges. This can be used to overwrite critical system files or create new files owned by root, potentially leading to a denial of service or privilege escalation (e.g., by modifying .rhosts). A temporary fix involves manually creating /tmp/dxchpwd.log as a root-owned file with restricted permissions.
Affected products
- Digital Equipment Corporation Digital Unix (OSF/1) 3.x
Timeline
- 1996-11-17: disclosed: Vulnerability reported to Bugtraq mailing list.
- 1996-11-17: advisory