Unauthenticated arbitrary file read through missing access control
Published Oct 23, 2023 · Updated Sep 11, 2024
Incorrect access control in carRental 1.0 allows remote attackers to read arbitrary files from the back-end system over the network. The published record identifies back-end file access as the vulnerable locus but does not disclose the endpoint, parameter, or failed authorization check. No authentication or user interaction is required, and exposure is limited to files readable by the back-end process.
Summary
What happened
Incorrect access control in carRental 1.0 allows remote attackers to read arbitrary files from the back-end system over the network. The published record identifies back-end file access as the vulnerable locus but does not disclose the endpoint, parameter, or failed authorization check. No authentication or user interaction is required, and exposure is limited to files readable by the back-end process.
The record
- CVE
- CVE-2023-33517
- Published
- Oct 23, 2023
- Updated
- Sep 11, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-552, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 23, 2023CVE publishedPublication date reported by the CVE source.
- Sep 11, 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.
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