Loading vulnerability…
mRemoteNG versions <= 1.76.20 and <= 1.77.3-dev load decrypted configuration files, including sensitive credentials, into process memory at application startup, regardless of whether a connection is established. This occurs even if the configuration files are encrypted on disk, and is exacerbated if no custom password encryption key is set. Attackers with access to process memory can extract plaintext credentials via memory dumps, effectively bypassing the on-disk encryption.
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 provides a proof-of-concept exploit for CVE-2023-30367, targeting mRemoteNG versions <= 1.77.3.1784-NB and <= 1.76.20 on Windows. The exploit consists of a C# tool (mRemoteNGDumper.exe) that locates the running mRemoteNG process, creates a full memory dump, and searches for decrypted configuration data within the dump. Extracted configuration files are saved as XML files in a 'dump' directory. These files may contain encrypted credentials, which can be decrypted using the included Python script (mremoteng_decrypt.py) with either the default key or via brute-force if a custom key is used. The exploit requires local access to the target system and does not provide remote code execution. The repository includes source code, build files, example extracted configuration files, and detailed usage instructions in the README. The main attack vector is local, relying on the ability to dump process memory and extract sensitive information.
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.