# CVE-2021-46335: Null dereference in n/a

> A NULL pointer dereference in the Moddable SDK allows attackers to cause a denial of service via the fx_Function_prototype_hasInstance component.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Jan 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-988q-3gg8-f4r5

## What is CVE-2021-46335?

CVE-2021-46335 is a medium-severity vulnerability in n/a, published on 20 Jan 2022. 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

Moddable SDK v11.5.0 was discovered to contain a NULL pointer dereference in the component fx_Function_prototype_hasInstance.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2021-46335?

It affects 1 product.


Products: Moddable Moddable Sdk.

## How do I fix CVE-2021-46335?

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

## Is CVE-2021-46335 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-46326](https://insights.sbomify.com/CVE-2021-46326/): Memory corruption in n/a (high 7.8)
- [CVE-2021-46328](https://insights.sbomify.com/CVE-2021-46328/): Memory corruption in n/a (high 7.8)
- [CVE-2021-46332](https://insights.sbomify.com/CVE-2021-46332/): Memory corruption in n/a (high 7.8)
- [CVE-2021-46334](https://insights.sbomify.com/CVE-2021-46334/): Memory corruption in n/a (high 7.8)
- [CVE-2021-46327](https://insights.sbomify.com/CVE-2021-46327/): Null dereference in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-46335 and fix it if it is affected.

What it is: CVE-2021-46335 is a medium-severity vulnerability in n/a, published on 20 Jan 2022. 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-2021-46335 in the wild and no public exploit code.

Affected product: n/a. 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-2021-46335/ (Markdown: https://insights.sbomify.com/CVE-2021-46335/index.md)
```

## Sources

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

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