# CVE-2016-11024: SQL Injection in odata4j

> SQL injection in odata4j allows attackers to read or modify database contents; the library is discontinued.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Mar 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-f96g-24cg-f24w

## What is CVE-2016-11024?

CVE-2016-11024 is a critical SQL injection vulnerability in n/a, published on 30 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

odata4j 0.7.0 allows ExecuteJPQLQueryCommand.java SQL injection. NOTE: this product is apparently discontinued.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2016-11024?

6 open source packages ship an affected version, including org.odata4j:odata4j-core, org.odata4j:odata4j-dist and org.odata4j:odata4j-parent. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.odata4j:odata4j-core` | Maven | All versions to 0.7.0 | None |
| `org.odata4j:odata4j-core` | Maven | All versions to 0.7.0 | None |
| `org.odata4j:odata4j-dist` | Maven | All versions to 0.7.0 | None |
| `org.odata4j:odata4j-dist` | Maven | All versions to 0.7.0 | None |
| `org.odata4j:odata4j-parent` | Maven | All versions to 0.7.0 | None |
| `org.odata4j:odata4j-parent` | Maven | All versions to 0.7.0 | None |

Products: Odata4j Project Odata4j.

## How do I fix CVE-2016-11024?

No fix has been published for CVE-2016-11024 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-11024 being exploited?

There is no known exploitation of CVE-2016-11024 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2016-11023](https://insights.sbomify.com/CVE-2016-11023/): SQL Injection in odata4j (critical 9.8)
- [CVE-2014-0171](https://insights.sbomify.com/CVE-2014-0171/): XML external entity in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-11024 and fix it if it is affected.

What it is: CVE-2016-11024 is a critical SQL injection vulnerability in n/a, published on 30 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-11024 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.odata4j:odata4j-core (Maven): affected all versions up to 0.7.0; no fix listed
- org.odata4j:odata4j-core (Maven): affected all versions up to 0.7.0; no fix listed
- org.odata4j:odata4j-dist (Maven): affected all versions up to 0.7.0; no fix listed
- org.odata4j:odata4j-dist (Maven): affected all versions up to 0.7.0; no fix listed
- org.odata4j:odata4j-parent (Maven): affected all versions up to 0.7.0; no fix listed
- org.odata4j:odata4j-parent (Maven): affected all versions up to 0.7.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-11024/ (Markdown: https://insights.sbomify.com/CVE-2016-11024/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-11024
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-11024
- OSV: https://osv.dev/vulnerability/CVE-2016-11024

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-11024/
Summaries are generated and may contain mistakes; the official description above is the record.