dbcve.org
Virus ScannerApplication · Bitdefender

CVE-2024-11128

HIGH · 7.8 CVSS v3.1 Published 2025-01-13
Fix available
A fix is available. Upgrade to 3.18 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability in the BitdefenderVirusScanner binary as used in Bitdefender Virus Scanner for MacOS may allow .dynamic library injection (DYLD injection) without being blocked by AppleMobileFileIntegrity (AMFI). This issue is caused by the absence of Hardened Runtime or Library Validation signing. This issue affects Bitdefender Virus Scanner versions before 3.18.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The BitdefenderVirusScanner binary for macOS lacks Hardened Runtime and Library Validation signing, allowing attackers to inject arbitrary dynamic libraries via DYLD environment variables. This injection bypasses AppleMobileFileIntegrity (AMFI) protections, enabling code execution in the context of the privileged scanner process.

MitigationUpgrade Bitdefender Virus Scanner for MacOS to version 3.18 or later which includes proper Hardened Runtime and Library Validation signing to block DYLD injection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Virus ScannerApplication
Affected:< 3.18

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Bitdefender Virus Scanner is installed
    Run: ls /Applications | grep -i 'Bitdefender' or check /Applications/Bitdefender Virus Scanner.app exists
    Affected if The application is present in /Applications
  2. Determine the installed version
    Run: defaults read /Applications/Bitdefender\ Virus\ Scanner.app/Contents/Info CFBundleShortVersionString or check the app's Info.plist for CFBundleShortVersionString
    Affected if Version number is below 3.18
  3. Verify Hardened Runtime is disabled
    Run: codesign -dv /Applications/Bitdefender\ Virus\ Scanner.app/Contents/MacOS/BitdefenderVirusScanner 2>&1 | grep -i runtime. If Hardened Runtime is disabled, the output will not contain 'runtime' or will show flags without runtime designation.
    Affected if Hardened Runtime is not enabled (output lacks 'runtime' in flags)
  4. Verify Library Validation is disabled
    Run: codesign -dv /Applications/Bitdefender\ Virus\ Scanner.app/Contents/MacOS/BitdefenderVirusScanner 2>&1 | grep -i library. If Library Validation is disabled, the output will not contain 'library' or will show flags without library validation.
    Affected if Library Validation is not enabled (output lacks library validation in flags)

Affected if Bitdefender Virus Scanner is installed with version below 3.18 AND the binary lacks both Hardened Runtime and Library Validation signing, allowing DYLD environment variable injection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.18 or later
Fixed in 3.18
Interim mitigation

Upgrade Bitdefender Virus Scanner for MacOS to version 3.18 or later which includes proper Hardened Runtime and Library Validation signing to block DYLD injection.

Recommended fix High confidence

Virus Scanner 3.18

  1. 1. Open Bitdefender Virus Scanner for Mac
  2. 2. Navigate to the application settings or check for updates
  3. 3. Update to Virus Scanner version 3.18 or later
  4. 4. Verify the update was successful by checking the installed version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Virus Scanner Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11128 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-11128 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data