# CVE-2024-5436: Type Confusion in Snapchat Lenscore

> Type confusion in Snapchat LensCore allows attackers to cause denial of service or execute arbitrary code.

- **Severity:** High 7.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:L/VI:H/VA:H/SC:L/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 May 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-5qx6-4rcv-pg8j

## What is CVE-2024-5436?

CVE-2024-5436 is a high-severity memory corruption vulnerability in Snapchat Lenscore, published on 31 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Type confusion in Snapchat LensCore could lead to denial of service or arbitrary code execution prior to version 12.88. We recommend upgrading to version 12.88 or above.

Weakness: CWE-843 (Access of Resource Using Incompatible Type), CWE-704 (Incorrect Type Conversion or Cast)

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

It affects 1 product.


Products: Snap Snapchat Lenscore.

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

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

## Is CVE-2024-5436 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-5436 is a high-severity memory corruption vulnerability in Snapchat Lenscore, published on 31 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-5436 in the wild and no public exploit code.

Affected product: Snapchat Lenscore. 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-5436/ (Markdown: https://insights.sbomify.com/CVE-2024-5436/index.md)
```

## Sources

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

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