Loading vulnerability…
KNX ETS5 versions up to and including 5.7.6 contain a vulnerability where a hard-coded password ('ETS5Password') and a fixed salt ('Ivan Medvedev') are used, allowing local users to access and read project information. This issue is present in products that are no longer supported by the vendor.
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 proof-of-concept exploit tool for CVE-2021-36799, a design flaw in KNX ETS5 project file encryption. The tool is written in C# (.NET Framework 4.6) and is structured as a Visual Studio solution. The main entry point is 'Program.cs', which invokes the 'PasswordRecovery' class to process project files stored in 'C:\ProgramData\KNX\ETS5\ProjectStore'. The tool loads various XML configuration files from this directory, decrypts sensitive fields using a hard-coded password and salt, and prints out secrets such as project passwords, device authentication codes, backbone keys, and more. The decryption logic is implemented in 'Deobfuscator.cs', which uses AES-CBC with static credentials. The exploit demonstrates that anyone with access to the project files can recover all secrets, highlighting the risk of the hard-coded encryption scheme. The repository includes source code, configuration, and documentation files, with the README providing detailed background on the vulnerability and its impact.
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.