# CVE-2024-11128: Insufficient Hardened Runtime or Library Validation signing in Bitdefender Virus Scanner for macOS

> Attackers can inject dynamic libraries into Bitdefender Virus Scanner on macOS due to missing Hardened Runtime signing, bypassing integrity checks.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Jan 2025
- **Updated:** 14 Jan 2025
- **Also known as:** GHSA-r88j-hwqm-286v

## What is CVE-2024-11128?

CVE-2024-11128 is a high-severity vulnerability in Bitdefender Virus Scanner, published on 13 Jan 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2024-11128?

It affects 1 product.


Products: Bitdefender Virus Scanner.

## How do I fix CVE-2024-11128?

No fix has been published for CVE-2024-11128 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-11128 being exploited?

There is no known exploitation of CVE-2024-11128 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-11128 and fix it if it is affected.

What it is: CVE-2024-11128 is a high-severity vulnerability in Bitdefender Virus Scanner, published on 13 Jan 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-11128 in the wild and no public exploit code.

Affected product: Bitdefender Virus Scanner. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-11128/ (Markdown: https://insights.sbomify.com/CVE-2024-11128/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-11128
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-11128
- OSV: https://osv.dev/vulnerability/CVE-2024-11128

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-11128/
Summaries are generated and may contain mistakes; the official description above is the record.
