Local code injection via absent library validation
Published Jan 13, 2025 · Updated Jan 14, 2025
DYLD injection in Bitdefender Virus Scanner before 3.18 allows local users to load unsigned libraries into the scanner process. The BitdefenderVirusScanner binary lacks Hardened Runtime or Library Validation signing, so AMFI does not block injected dynamic libraries. Exploitation requires local low-privilege access and active user interaction; injected code can read or alter data available to the scanner.
Summary
What happened
DYLD injection in Bitdefender Virus Scanner before 3.18 allows local users to load unsigned libraries into the scanner process. The BitdefenderVirusScanner binary lacks Hardened Runtime or Library Validation signing, so AMFI does not block injected dynamic libraries. Exploitation requires local low-privilege access and active user interaction; injected code can read or alter data available to the scanner.
The record
- CVE
- CVE-2024-11128
- Published
- Jan 13, 2025
- Updated
- Jan 14, 2025
- Vendor
- Bitdefender
- Product
- Bitdefender Virus Scanner
- Classifications
- CWE-269, CAPEC-233, T1574.006
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 13, 2025CVE publishedPublication date reported by the CVE source.
- Jan 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.18
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo