Loading vulnerability…
CVE-2024-57040 affects TP-Link TL-WR845N(UN) firmware versions V4_200909 and V4_190219. The vulnerability is a hardcoded password for the root account embedded in the device firmware. According to the provided information, the credential can be recovered by analyzing downloaded firmware images, and may also be obtainable through brute-force attempts with physical access to the router. This constitutes the use of a static, embedded privileged credential in the affected router firmware.
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 Python exploit script (CVE-2024-57040.py) targeting TP-Link TL-WR845N(UN) routers with specific firmware versions (V4_190219, V4_200909, V4_201214) affected by CVE-2024-57040. The vulnerability is due to a hardcoded root password (admin:1234). The script uses the Paramiko library to establish an SSH connection to the router using these credentials, providing the attacker with an interactive shell for remote command execution. The exploit requires the router to be in a factory default state with unchanged credentials and SSH enabled. The repository also includes a README.md with vulnerability details, a LICENSE file (Apache 2.0), and a .gitignore. The main entry point is CVE-2024-57040.py, and the attack vector is network-based via SSH.
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.
5 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.