Unauthenticated local-file disclosure via WEB-INF traversal
Published Jan 18, 2021 · Updated Sep 17, 2024
Path traversal in Atlassian FishEye and Crucible before 4.8.5 allows remote attackers to read local files through WEB-INF requests. The vendor identifies the WEB-INF request path as the vulnerable locus but does not disclose the endpoint or failed authorization operation. No authentication or user interaction is required, and the documented impact is limited to local-file disclosure.
Summary
What happened
Path traversal in Atlassian FishEye and Crucible before 4.8.5 allows remote attackers to read local files through WEB-INF requests. The vendor identifies the WEB-INF request path as the vulnerable locus but does not disclose the endpoint or failed authorization operation. No authentication or user interaction is required, and the documented impact is limited to local-file disclosure.
The record
- CVE
- CVE-2020-29446
- Published
- Jan 18, 2021
- Updated
- Sep 17, 2024
- Vendor
- Atlassian
- Product
- FishEye
- Classifications
- CWE-639, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 18, 2021CVE publishedPublication date reported by the CVE source.
- Sep 17, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <4.8.5
What conditions does exploitation require?
What is affected?
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo