CVE-2017-10974: Path Traversal
First published: Fri Jul 07 2017(Updated: )
Yaws 1.91 allows Unauthenticated Remote File Disclosure via HTTP Directory Traversal with /%5C../ to port 8080. NOTE: this CVE is only about use of an initial /%5C sequence to defeat traversal protection mechanisms; the initial /%5C sequence was apparently not discussed in earlier research on this product.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Yaws | =1.91 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-10974?
CVE-2017-10974 is classified as a medium severity vulnerability due to its potential for unauthorized remote file disclosure.
How do I fix CVE-2017-10974?
To fix CVE-2017-10974, update Yaws to the latest version or apply patches that address this directory traversal vulnerability.
What versions of Yaws are affected by CVE-2017-10974?
CVE-2017-10974 affects Yaws version 1.91.
What type of vulnerability is CVE-2017-10974?
CVE-2017-10974 is a remote file disclosure vulnerability caused by HTTP directory traversal.
Can CVE-2017-10974 be exploited without authentication?
Yes, CVE-2017-10974 can be exploited without authentication, allowing unauthenticated users to access sensitive files.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/weakness
- agent/last-modified-date
- agent/references
- agent/author
- agent/event
- agent/description
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/yaws
- canonical/yaws
- version/yaws/1.91