CVE-2020-24719 is an information exposure vulnerability in version 6.5.1 of the affected Erlang-based software, where the Erlang node authentication secret (the "magic cookie") may be written into log content. Erlang distributed node communication relies on this shared secret for trust establishment between nodes. If an attacker obtains the cookie from exposed logs, they can authenticate to the Erlang node, attach to it as a trusted peer, and execute OS-level commands on the host system. The issue is fixed in version 6.6.0.
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 module: 'Erlang Port Mapper Daemon Cookie RCE' (modules/exploits/multi/misc/erlang_cookie_rce.rb). The module exploits the Erlang Port Mapper Daemon (EPMD) when the attacker knows the authentication cookie (typically stored in the '.erlang.cookie' file). By authenticating as a trusted node, the attacker can execute arbitrary commands on the target system. The exploit supports multiple platforms (Unix, Linux, Windows) and can deliver various Metasploit payloads, such as reverse shells or user creation. The main attack vector is network-based, targeting TCP port 25672. The exploit is weaponized, as it is part of the Metasploit framework and supports customizable payloads. The only fingerprintable endpoints are the EPMD TCP port (25672) and the '.erlang.cookie' file used for authentication.
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.