
Cloud Vulnerability DB
A community-led vulnerabilities database
odata4j 0.7.0 contains a SQL injection vulnerability in ExecuteCountQueryCommand.java. The vulnerability was discovered in May 2016 and publicly disclosed in March 2020, receiving the identifier CVE-2016-11023. This vulnerability affects the odata4j-dist-0.7.0.jar package, specifically in the org.odata4j.producer.jpa package (Google Groups).
The SQL injection vulnerability exists in ExecuteCountQueryCommand.java at line 18. The vulnerability allows for SQL injection through improper input validation. The severity is rated as CRITICAL with a CVSS v3.1 base score of 9.8 (Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) (NVD).
If successfully exploited, this vulnerability could allow an attacker to execute arbitrary SQL commands on the underlying database, potentially leading to unauthorized access, data manipulation, or data disclosure (NVD).
Two recommended mitigations have been suggested: 1) Migrate to alternative OData implementations such as Apache Olingo, or 2) Avoid using the org.odata4j.producer.jpa package. Note that the product is apparently discontinued and no official patches are available (Google Groups).
Source: This report was generated using AI
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."