Loading vulnerability…
Bangkok Medical Software HOSxP XE v4.64.11.3 contains a hardcoded IDEA encryption Key-IV pair in the HOSxPXE4.exe and HOS-WIN32.INI components. This implementation flaw allows attackers with access to the software or configuration files to retrieve the static cryptographic keys, enabling decryption of sensitive data protected by the application.
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 PowerShell proof-of-concept exploit for CVE-2024-53522, a vulnerability in HOSxP XE version 4.64.11.3. The vulnerability arises from the use of hard-coded cryptographic keys and IVs in the application's configuration file encryption. The main script, CVE-2024-53522.ps1, implements the IDEA cipher (ported from DCPCrypt) and uses static key and IV values to decrypt sensitive fields from the HOS-WIN32.INI configuration file. When run, the script extracts and decrypts database credentials and gateway information, exposing them in plaintext. The exploit requires local access to the target system and knowledge of the configuration file's location (default: C:\ProgramData\HOS-WIN32.INI). The repository also includes a README with background information and a standard MIT license. No network endpoints are targeted; the attack vector is local file access and decryption.
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.