Loading vulnerability…
CVE-2024-2997 is a cross-site scripting (XSS) vulnerability in Bdtask Multi-Store Inventory Management System up to version 20240320. The vulnerability exists in the handling of user-supplied input for the fields Category Name, Model Name, Brand Name, and Unit Name. Unsanitized input in these fields is rendered in the application, allowing attackers to inject arbitrary JavaScript code. The vulnerability can be exploited remotely and does not require authentication. The vendor has not responded to disclosure attempts, and a public exploit is available.
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 (4 hidden).
Repository contains a standalone Python-based network scanner/exploit for CVE-2024-2997. The main file `CVE-2024-2997.py` performs multi-threaded scanning (default 20 threads) against a generated list of candidate URLs derived from a user-supplied base URL, with session save/resume via `scope.txt`. For each target URL, it issues HTTP requests (via `requests`, TLS warnings disabled) to a specific path `/cmd,/simZysh/register_main/setCookie` with crafted query parameter `c0=...` that injects Python expressions calling `subprocess.check_output()` or `os.system/os.popen` to execute commands like `id`, `whoami`, and `echo CVE20242997VULN`. Responses are evaluated using a large set of indicators (Unix uid/gid strings, Windows tokens, and generic error/vuln strings) to classify confidence (Low/Medium/High/Critical per README) and to detect “similar vulnerabilities” as well. Outputs: vulnerable URLs are appended to `sus.txt`; detailed per-finding information is written to `vulnerable_details.txt`; the README indicates an HTML report `report.html` and raw response captures `response_*.txt` for confirmed cases. The script supports optional proxying (`-p/--proxy`), configurable timeouts/delays/batch size, verbose mode, and interactive operation. `setup_and_run.bat` installs dependencies (requests/urllib3/colorama) and runs the scanner. Overall purpose: automated discovery and basic exploitation/verification of a command-injection/RCE condition consistent with CVE-2024-2997 by attempting benign commands and matching output in HTTP 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.