Loading vulnerability…
CVE-2022-38121 affects UPSMON PRO. The product stores user passwords in plaintext within a configuration file located under a public user directory. Because the file is insufficiently protected, a remote attacker with only general user privileges can access the configuration file and recover account names and corresponding passwords for all users, including administrators. The core issue is insecure storage of sensitive authentication data in plaintext combined with exposure of that file to lower-privileged users.
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 auxiliary module (modules/auxiliary/gather/upsmon_traversal.rb) targeting POWERCOM UPSMON PRO <= v2.61. The module exploits a path traversal vulnerability (CVE-2022-38120) to retrieve arbitrary files from the target system via HTTP requests. By default, it attempts to retrieve the UPSMON.ini configuration file, which contains sensitive credentials for the web service, mail server, application, and SMS service (CVE-2022-38121). The module parses the retrieved INI file and extracts credentials, storing them in the Metasploit database. The exploit is operational, requiring the attacker to specify the target's base path, file to retrieve, and traversal depth. The default endpoint is the web interface on port 8000. The code is written in Ruby and is designed to be used within the Metasploit framework.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.