# CVE-2024-24293: MiguelCastillo @bit/loader Prototype Pollution issue

> Attackers can execute arbitrary code via prototype pollution in the @bit/loader library, requiring developers to upgrade the package.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 May 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-8vr4-h4rr-8ph6

## What is CVE-2024-24293?

CVE-2024-24293 is a high-severity code injection vulnerability in n/a, published on 20 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A Prototype Pollution issue in MiguelCastillo @bit/loader v.10.0.3 allows an attacker to execute arbitrary code via the M function e argument in index.js.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

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

2 open source packages ship an affected version, including @bit/loader.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@bit/loader` | npm | All versions to 10.0.3 | None |
| `@bit/loader` | npm | All versions to 10.0.3 | None |

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

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

## Is CVE-2024-24293 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-24293 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-24293 is a high-severity code injection vulnerability in n/a, published on 20 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-24293 exists.

Affected packages and fixed versions:
- @bit/loader (npm): affected all versions up to 10.0.3; no fix listed
- @bit/loader (npm): affected all versions up to 10.0.3; no fix listed

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-24293/ (Markdown: https://insights.sbomify.com/CVE-2024-24293/index.md)
```

## Sources

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

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