odata4j vulnerabilities and fixes

Recent CVEs affecting odata4j, with upgrade or downgrade steps. 2 tracked.

odata4j has 2 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 0. Most recent: 2020-03-30. Highest priority: CVE-2016-11024 (score 57/100).

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

FAQ

How do I fix odata4j vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is odata4j being exploited right now?

None of the tracked odata4j CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which odata4j CVE should I patch first?

CVE-2016-11024 currently ranks highest (57/100): odata4j 0.7.0 allows ExecuteJPQLQueryCommand.java SQL injection.

← Back to latest CVEs