Loading vulnerability…
CVE-2023-3349 is an information exposure vulnerability in IBERMATICA RPS 2019. An unauthenticated user can access a status endpoint that enables the application's logging mechanism and causes a log file to be generated and made available for download. The exposed log data can include sensitive operational and application information such as usernames, IP addresses, and SQL queries submitted to the application. The issue stems from improper exposure of diagnostic or logging functionality to unauthenticated users.
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.
Repository contains a minimal proof-of-concept for the IBERMATICA RPS 2019 vulnerability chain involving CVE-2023-3349 and CVE-2023-3350. Structure is simple: one C# source file, a README with the attack narrative and remediation guidance, and a license file. The main code file, CVE-2023-3350.cs, is a standalone console program that uses RijndaelManaged in CBC mode to decrypt a Base64 ciphertext with a 16-byte key and IV. Both values are hardcoded placeholders ('bbbbbbbbbUSER_XX' and 'bbbbbbbbbPASS_XX'), reflecting the README’s claim that keying material is predictably derived from usernames and reused as IV material. The program’s capability is limited to local decryption of an already obtained encrypted password value; it does not automate log retrieval, status-page interaction, authentication bypass, or remote exploitation. The README documents the broader attack chain: an unauthenticated attacker accesses /RPS2019Service/status.html, enables or downloads logs, extracts usernames and encrypted password values from logged SQL queries, derives the AES material, and recovers plaintext passwords. Because the repository does not include code to interact with the web endpoint and instead only demonstrates the cryptographic weakness, it is best classified as a POC exploit component rather than a full operational exploit.
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.