Loading vulnerability…
OrientDB versions through 2.2.22 fail to enforce privilege requirements when processing queries that use the 'where', 'fetchplan', or 'order by' clauses. This allows remote attackers to craft requests that bypass intended access controls and execute arbitrary operating system commands.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a single Metasploit module (modules/exploits/multi/http/orientdb_exec.rb) that exploits a remote code execution vulnerability (CVE-2017-11467) in OrientDB versions 2.2.2 through 2.2.22. The exploit leverages a privilege escalation flaw to create and execute unsandboxed OS commands via the OrientDB REST API. The module supports Linux, Unix, and Windows targets, and can deliver arbitrary payloads using Metasploit's command stagers. The attacker must have valid HTTP Basic Auth credentials (default: writer/writer). The exploit interacts with several OrientDB HTTP endpoints to list databases, create and trigger malicious functions, and manage user privileges. The code is weaponized, as it is part of the Metasploit framework and supports customizable payloads. The repository is structured as a single Ruby file implementing the exploit logic, with clear separation of functions for checking vulnerability, executing commands, and cleaning up after exploitation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.