CVE-2016-11023: odata4j 0.7.0 allows ExecuteCountQueryCommand.java SQL injection

This month

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2016-11023 is a critical-severity flaw (CVSS 9.8) affecting odata4j. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

Critical severity
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.4% (top 27%)
CISA exploited list	No
Weakness	CWE-89
Published	2020-03-30
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: odata4j project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-03-30 20:15 UTCPublished CVE record published
2026-06-17 00:40 UTCUpdated Record last modified

odata4j project odata4j DOWNGRADE

Affected: 0.7

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.7

1. Check installed version

apt-cache policy odata4j || rpm -q odata4j || odata4j --version

2. No fixed release: DOWNGRADE to a release before 0.7 (Debian / Ubuntu)

apt-cache madison odata4j sudo apt install odata4j=<VERSION_BEFORE_0.7> sudo apt-mark hold odata4j

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list odata4j sudo dnf downgrade odata4j-<VERSION_BEFORE_0.7> sudo dnf versionlock add odata4j

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2016-11023?

odata4j: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2016-11023 being exploited?

CVE-2016-11023 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2016-11023 affect?

CVE-2016-11023 affects odata4j. Severity is critical (CVSS 9.8). odata4j 0.7.0 allows ExecuteCountQueryCommand.java SQL injection. NOTE: this product is apparently discontinued.

How urgent is CVE-2016-11023?

Priority 57/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

Java vulnerabilities

Related CVEs

CVE-2016-11024 CRITICAL 9.8 DOWNGRADE odata4j 0.7.0 allows ExecuteJPQLQueryCommand.java SQL injection

References

← Back to latest CVEs