Loading vulnerability…
CVE-2022-29845 is a vulnerability in Progress (formerly Ipswitch) WhatsUp Gold versions 21.1.0 through 21.1.1 and 22.0.0. The flaw allows an authenticated user to invoke a specific API transaction that can read the contents of arbitrary local files on the server. This vulnerability is categorized as CWE-829 (Inclusion of Functionality from Untrusted Control Sphere). The attack requires authentication but is otherwise of low complexity and can be performed remotely over the network.
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.
This repository contains a single Metasploit post-exploitation module: 'whatsupgold_credential_dump.rb'. The module is designed to extract and decrypt credentials from WhatsUp Gold installations on Windows systems. It supports WhatsUp Gold versions 11.0 through 22.x and targets several CVEs (CVE-2022-29845 through CVE-2022-29848). The module can export the WhatsUp Gold SQL database to a CSV file, decrypt the credentials stored within, and add the recovered credentials to Metasploit's loot system. It provides three main actions: 'Dump' (export and decrypt), 'Export' (export only), and 'Decrypt' (decrypt an existing export). The module requires a Meterpreter session on a Windows host with WhatsUp Gold installed. The code is written in Ruby and leverages Metasploit's post-exploitation and credential management APIs. No network endpoints are directly targeted; instead, the module interacts with local files and the Windows registry to perform its actions.
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.