Loading vulnerability…
CVE-2024-5124 is a timing attack vulnerability in the gaizhenbiao/chuanhuchatgpt repository, version 20240310. The vulnerability is due to the use of the '=' operator for password comparison in Python, which results in non-constant time comparison. This allows an attacker to infer correct password characters by measuring the time taken for each comparison, potentially leading to password disclosure.
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 proof-of-concept exploit for CVE-2024-5124, targeting the ChuanhuChatbot application (Docker image tuchuanhuhuhu/chuanhuchatgpt:20240310). The exploit consists of two main Python scripts: main.py and step2like.py. The main.py script performs repeated POST requests to the victim server's /login endpoint, measuring response times for different password guesses to conduct a timing side-channel attack. The step2like.py script generates timing probes and logs results for further analysis. The README.md provides detailed setup instructions for both the victim server (using Docker) and the exploit environment (using Python virtual environments and required libraries). The exploit is operational as a proof-of-concept and outputs timing data and analysis files (such as box_plot.png) to help infer valid credentials. The main network endpoint targeted is https://29f8a8329e423aad91.gradio.live/login, and the attack vector is network-based, leveraging timing differences in authentication responses.
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.