Loading vulnerability…
CVE-2024-51996 is an authentication bypass vulnerability in Symfony's remember-me functionality, specifically in handling persisted remember-me cookies within the security-http component. When Symfony consumes a persisted remember-me cookie, it fails to verify that the username associated with the cookie matches the username stored for the corresponding persisted token in the database. This improper validation can allow a mismatch between cookie-supplied identity data and server-side persisted token data to be accepted, resulting in authentication being granted incorrectly. The issue was fixed by updating the PersistentRememberMeHandler logic to enforce username matching. Fixed versions are 5.4.47, 6.4.15, and 7.1.8.
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 Python proof-of-concept exploit for CVE-2024-51996, a critical authentication bypass vulnerability in Symfony's 'Remember Me' feature. The exploit script (CVE-2024-51996.py) takes as input a target URL, a stolen REMEMBERME cookie, and a username to impersonate (e.g., 'admin'). It forges a new REMEMBERME cookie by replacing the original username with the target username and sends an HTTP request to the target application with this cookie. If the application is vulnerable, the attacker may gain access as the impersonated user, potentially bypassing authentication and accessing privileged areas. The repository also includes a README.md with detailed usage instructions and background on the vulnerability. No detection or fake code is present; the exploit is functional and focused on demonstrating the vulnerability.
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.