Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven
Not in CISA KEV
CRITICAL severity

CVE-2016-11023

CRITICAL

CVE-2016-11023 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in org.odata4j:odata4j-core. O3 Security confirms whether CVE-2016-11023 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

SQL Injection in odata4j

Also known asGHSA-2382-qx5h-rvqh
Published
Mar 30, 2020
Updated
Jul 8, 2026
Affected
3 pkgs
Patched
None yet
Exploits
None indexed
Exploitation data as of Jul 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

3 pkgs affected
org.odata4j:odata4j-coreorg.odata4j:odata4j-distorg.odata4j:odata4j-parent

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

3 total
EcosystemPackageVulnerable rangeFix
Mavenorg.odata4j:odata4j-coreall versionsNo fix
Mavenorg.odata4j:odata4j-distall versionsNo fix
Mavenorg.odata4j:odata4j-parentall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.odata4j:odata4j-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of org.odata4j:odata4j-core has shipped for CVE-2016-11023 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2016-11023 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2016-11023. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

odata4j 0.7.0 allows ExecuteCountQueryCommand.java SQL injection. NOTE: this product is apparently discontinued.
O3 Security · Impact-Aware SCA

Is CVE-2016-11023 in your dependencies?

O3 detects CVE-2016-11023 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

CVE-2016-11023: SQL Injection in odata4j… | O3 Security