CVE-2022-29056 is an improper restriction of excessive authentication attempts vulnerability in Fortinet FortiMail. Affected versions are 6.4.0, 6.2.0 through 6.2.4, and versions before 6.0.9. The flaw is present in the HTTP login interface, where numerous requests to the login form can trigger partial exhaustion of CPU and memory resources. The issue indicates insufficient controls on repeated authentication-related requests, enabling unauthenticated remote abuse of the login endpoint.
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 small Python proof-of-concept labeled CVE-2022-29056 with a Tkinter GUI front-end. Structure: - README.md: Portuguese description stating it is an educational automation script to send repeated requests to a login endpoint and vary payload size. - exploit.py: Main script. Provides a GUI to input a target IPv4 address and a payload size, validates the IP via regex, then starts a background thread that repeatedly POSTs to https://<target_ip>/logincheck every 2 seconds until stopped. Exploit capabilities: - Network-based request automation against a specific login path (/logincheck). - Generates oversized form fields (username and password) of operator-chosen length; username is prefixed with a single quote and suffixed with '#', which resembles basic injection/probing patterns. - Prints HTTP status code and full response body for each request. Notable implementation details/limitations: - TLS verification is disabled (verify=False). - Uses a hardcoded csrfmiddlewaretoken value, which may not be valid for real sessions and could limit effectiveness unless the target accepts it. - No vulnerability verification logic beyond observing responses; no RCE, shell, or privilege escalation payloads included.
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.
1 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.