File overwrite via dot-dot path traversal
Published Feb 4, 2000 · Updated Aug 1, 2024
Path traversal in ypbind on Slackware Linux and SunOS allows remote attackers to overwrite files through crafted requests. The CVE record describes a dot-dot attack but does not disclose the affected path-building code or file-content constraints. Exploitation requires the -ypset or -ypsetme options to be enabled; local users are also affected.
Summary
What happened
Path traversal in ypbind on Slackware Linux and SunOS allows remote attackers to overwrite files through crafted requests. The CVE record describes a dot-dot attack but does not disclose the affected path-building code or file-content constraints. Exploitation requires the -ypset or -ypsetme options to be enabled; local users are also affected.
The record
- CVE
- CVE-1999-0298
- Published
- Feb 4, 2000
- Updated
- Aug 1, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 4, 2000CVE publishedPublication date reported by the CVE source.
- Aug 1, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us