CVE-2024-4890 is a blind SQL injection vulnerability in berriai/litellm version 1.27.14. The vulnerability is present in the '/team/update' endpoint, where the 'user_id' parameter is improperly sanitized before being used in a raw SQL query for user deletion. This allows attackers to inject arbitrary SQL commands via the 'user_id' parameter.
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 is a proof-of-concept (PoC) exploit for CVE-2024-4890, a privilege escalation vulnerability in the 'needrestart' utility on Linux (version 3.8+). The exploit leverages insecure handling of the PYTHONPATH environment variable by needrestart when run with sudo. The attacker prepares a malicious shared object (__init__.so, compiled from lib.c) and places it in a fake importlib directory structure under /tmp/malicious. A bait Python script (e.py) is run with PYTHONPATH set to this directory, and a shell script (runner.sh) automates the setup. When needrestart is triggered with sudo, it scans the bait process, loads the attacker's shared object as root, and executes the payload. The payload creates a SUID root shell at /tmp/poc and adds a sudoers rule for persistence. The repository contains three main code files: lib.c (payload), main.py (minimal bait loop), and runner.sh (automation script). The exploit is operational and provides reliable root access on vulnerable systems.
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.