Unauthenticated data exposure and modification
Published Apr 16, 2024 · Updated Nov 5, 2024
Data exposure in Oracle Complex Maintenance, Repair, and Overhaul 12.2.3 through 12.2.13 allows remote attackers to read and alter data via HTTP. Oracle identifies the affected locus only as the LOV component and has not published the untrusted input or incorrect operation involved. Exploitation is unauthenticated but requires another person to interact; successful attacks can read a subset of accessible data and update, insert, or delete some accessible data.
Summary
What happened
Data exposure in Oracle Complex Maintenance, Repair, and Overhaul 12.2.3 through 12.2.13 allows remote attackers to read and alter data via HTTP. Oracle identifies the affected locus only as the LOV component and has not published the untrusted input or incorrect operation involved. Exploitation is unauthenticated but requires another person to interact; successful attacks can read a subset of accessible data and update, insert, or delete some accessible data.
The record
- CVE
- CVE-2024-21017
- Published
- Apr 16, 2024
- Updated
- Nov 5, 2024
- Vendor
- Oracle
- Product
- Oracle Complex Maintenance, Repair, and Overhaul
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 16, 2024CVE publishedPublication date reported by the CVE source.
- Nov 5, 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=12.2.3 <=12.2.13
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
No sourced classifications are available.
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