Unauthenticated file disclosure via exposed web directory
Published Sep 10, 2024 · Updated Sep 12, 2024
File exposure in MERCURY MNVR816 2.0.1.0.0 through 2.0.1.0.5 allows remote attackers to read files via /web-static/. The /web-static/ path serves files or directories without enforcing authorization, while the affected handler and input manipulation remain undisclosed. No authentication or user interaction is required, and the published impact is limited to confidentiality.
Summary
What happened
File exposure in MERCURY MNVR816 2.0.1.0.0 through 2.0.1.0.5 allows remote attackers to read files via /web-static/. The /web-static/ path serves files or directories without enforcing authorization, while the affected handler and input manipulation remain undisclosed. No authentication or user interaction is required, and the published impact is limited to confidentiality.
The record
- CVE
- CVE-2024-8655
- Published
- Sep 10, 2024
- Updated
- Sep 12, 2024
- Vendor
- MERCURY
- Product
- MNVR816 firmware
- Classifications
- CWE-552, T1083
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 10, 2024CVE publishedPublication date reported by the CVE source.
- Sep 12, 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=2.0.1.0.0 <=2.0.1.0.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