CVE-2016-11024: SQL Injection
First published: Mon Mar 30 2020(Updated: )
odata4j 0.7.0 allows ExecuteJPQLQueryCommand.java SQL injection. NOTE: this product is apparently discontinued.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Odata4j | =0.7 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2016-11024?
The severity of CVE-2016-11024 is classified as high due to the potential for SQL injection attacks.
How do I fix CVE-2016-11024?
To fix CVE-2016-11024, it's recommended to upgrade to a version of Odata4j that is not affected, though the product is discontinued.
What software is affected by CVE-2016-11024?
CVE-2016-11024 affects Odata4j version 0.7.0.
Can CVE-2016-11024 lead to data exposure?
Yes, CVE-2016-11024 can lead to unauthorized access and exposure of sensitive data through SQL injection.
Is Odata4j still maintained in light of CVE-2016-11024?
No, Odata4j appears to be a discontinued project, which means CVE-2016-11024 won't receive official patches.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/author
- agent/last-modified-date
- agent/severity
- agent/references
- agent/first-publish-date
- agent/event
- agent/description
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/odata4j project
- canonical/odata4j
- version/odata4j/0.7