CVE-2017-11467

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 76.3%, top 1% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Weaponized
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 73%
CISA-KEV: Not listedEPSS: 73%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

OrientDB through 2.2.22 does not enforce privilege requirements during "where" or "fetchplan" or "order by" use, which allows remote attackers to execute arbitrary OS commands via a crafted request.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
99.4%
KEV
Not listed

Published

July 20, 2017

Last Modified

May 13, 2026

Advisory Details (1)

Auto-updated May 18, 2026
No patch confirmed yet.
generic

Home · orientechnologies/orientdb Wiki · GitHub

https://github.com/orientechnologies/orientdb/wiki/OrientDB-2.2-Release-Notes#2223---july-11-2017

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
com.orientechnologies:orientdb-core1.0 ... 2.2.9 (112 versions)2.2.23—

Data Freshness Timeline

(refreshed 6× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 02:20 UTCEPSS rescore
  2. 2026-07-04 06:28 UTCEPSS rescore
  3. 2026-07-01 15:02 UTCEPSS rescore
  4. 2026-07-01 15:02 UTCEPSS rescore
  5. 2026-06-30 23:19 UTCEPSS rescore
  6. 2026-06-30 23:19 UTCEPSS rescore
  7. 2026-06-29 14:03 UTCEPSS rescore
  8. 2026-06-27 03:05 UTCEPSS rescore
  9. 2026-06-25 13:47 UTCEPSS rescore
  10. 2026-06-25 13:47 UTCEPSS rescore
  11. 2026-06-23 21:30 UTCEPSS rescore
  12. 2026-06-19 19:23 UTCEPSS rescore
  13. 2026-06-19 19:23 UTCEPSS rescore
  14. 2026-06-18 17:50 UTCEPSS rescore
  15. 2026-06-17 17:50 UTCEPSS rescore
  16. 2026-06-16 17:50 UTCEPSS rescore
  17. 2026-06-15 17:45 UTCEPSS rescore
  18. 2026-06-14 23:14 UTCEPSS rescore
  19. 2026-06-14 23:14 UTCEPSS rescore
  20. 2026-06-12 23:09 UTCEPSS rescore
  21. 2026-06-11 13:57 UTCEPSS rescore
  22. 2026-06-10 22:15 UTCEPSS rescore
  23. 2026-06-08 14:14 UTCEPSS rescore
  24. 2026-06-07 15:22 UTCEPSS rescore
  25. 2026-06-07 15:22 UTCEPSS rescore
Show 29 more
  1. 2026-06-06 13:45 UTCEPSS rescore
  2. 2026-06-06 13:45 UTCEPSS rescore
  3. 2026-06-05 22:44 UTCEPSS rescore
  4. 2026-06-05 06:08 UTCEPSS rescore
  5. 2026-06-05 06:08 UTCEPSS rescore
  6. 2026-06-01 13:49 UTCEPSS rescore
  7. 2026-06-01 13:49 UTCEPSS rescore
  8. 2026-05-31 22:28 UTCEPSS rescore
  9. 2026-05-31 00:14 UTCEPSS rescore
  10. 2026-05-29 13:41 UTCEPSS rescore
  11. 2026-05-28 13:42 UTCEPSS rescore
  12. 2026-05-28 13:42 UTCEPSS rescore
  13. 2026-05-26 07:17 UTCEPSS rescore
  14. 2026-05-26 07:17 UTCEPSS rescore
  15. 2026-05-23 00:10 UTCEG score recompute
  16. 2026-05-22 21:15 UTCEPSS rescore
  17. 2026-05-22 21:15 UTCEPSS rescore
  18. 2026-05-22 21:15 UTCEPSS rescore
  19. 2026-05-20 08:04 UTCEG score recompute
  20. 2026-05-20 04:06 UTCEG score recompute
  21. 2026-05-20 00:08 UTCEG score recompute
  22. 2026-05-19 20:10 UTCEG score recompute
  23. 2026-05-19 16:12 UTCEG score recompute
  24. 2026-05-19 12:13 UTCEG score recompute
  25. 2026-05-19 08:14 UTCEG score recompute
  26. 2026-05-19 04:16 UTCEG score recompute
  27. 2026-05-19 00:18 UTCEG score recompute
  28. 2026-05-18 21:30 UTCEPSS rescore
  29. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Metasploit module) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-44068
    First seen Jul 13, 2017

    OrientDB - Code Execution

    Open source ↗
  • Metasploitexploit/multi/http/orientdb_exec✓ verified
    First seen Jul 13, 2017

    OrientDB 2.2.x Remote Code Execution

    Open source ↗

Frequently asked(5)

What is CVE-2017-11467?
CVE-2017-11467 is a critical vulnerability published on July 20, 2017. OrientDB through 2.2.22 does not enforce privilege requirements during "where" or "fetchplan" or "order by" use, which allows remote attackers to execute arbitrary OS commands via a crafted request.
When was CVE-2017-11467 disclosed?
CVE-2017-11467 was first published in the National Vulnerability Database on July 20, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-11467 actively exploited?
CVE-2017-11467 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-11467?
CVE-2017-11467 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-11467?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-11467, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-11467

Explore →

Is Your Infrastructure Affected by CVE-2017-11467?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs