Lexmark products up to 2023-01-10 are affected by an Improper Control of Interaction Frequency vulnerability. This issue arises when the product does not adequately limit or control the rate or frequency of user interactions, potentially allowing an attacker to abuse the functionality, such as by launching denial-of-service attacks or bypassing intended usage restrictions.
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 two Python proof-of-concept scripts targeting CVE-2023-22960, a vulnerability in Lexmark printers' Embedded Web Server interface (firmware before 01/2023). The vulnerability allows attackers to bypass the brute-force prevention mechanism for both username/password and PIN-based authentication. The scripts, 'lexmark-brute-force-login.py' and 'lexmark-brute-force-pins.py', automate brute-force attacks against the '/webglue/session/create' endpoint over HTTP or HTTPS. The attacker supplies a target IP/domain, protocol, and lists of usernames/passwords or PINs. The scripts use multithreading to maximize login attempts, exploiting the flaw to enumerate valid credentials. The repository is structured with a README (explaining the vulnerability and usage), a license, and the two exploit scripts. No detection or fake code is present; both scripts are functional PoCs for the described vulnerability.
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.