Loading vulnerability…
In Apache Rave versions 0.11 through 0.20, the users/get program in the User RPC API allows remote authenticated users to obtain sensitive information about all user accounts by manipulating the offset parameter. This flaw exposes the password field in the API response, which may contain password hashes, thereby leaking sensitive credential information.
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 (2 hidden).
This repository contains a single Metasploit auxiliary module (modules/auxiliary/gather/apache_rave_creds.rb) targeting an information disclosure vulnerability (CVE-2013-1814) in Apache Rave 0.20 and earlier. The module attempts to authenticate to the Apache Rave portal using either user-supplied credentials or a set of known default accounts. Upon successful authentication, it exploits a flaw in the RPC API endpoint (/app/api/rpc/users/get) to retrieve information about all users, including their usernames and password hashes. The module saves the retrieved data and reports discovered credentials to the Metasploit database. The exploit is operational, requiring valid credentials (either default or user-supplied) and network access to the Apache Rave portal (default path /portal, port 8080). The code is written in Ruby and is structured as a standard Metasploit module, making use of the framework's HTTP client and credential reporting features.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.