Unauthenticated SQL execution via count-query injection
Published Mar 30, 2020 · Updated Aug 6, 2024
SQL injection in odata4j 0.7.0 allows remote attackers to execute arbitrary SQL through the ExecuteCountQueryCommand component. Published records name ExecuteCountQueryCommand.java as the vulnerable locus but do not disclose which input reaches the query or the unsafe query-building operation. Network access requires no authentication or user interaction; successful injection gives attackers control over the database query run by a consuming application.
Summary
What happened
SQL injection in odata4j 0.7.0 allows remote attackers to execute arbitrary SQL through the ExecuteCountQueryCommand component. Published records name ExecuteCountQueryCommand.java as the vulnerable locus but do not disclose which input reaches the query or the unsafe query-building operation. Network access requires no authentication or user interaction; successful injection gives attackers control over the database query run by a consuming application.
The record
- CVE
- CVE-2016-11023
- Published
- Mar 30, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 30, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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