# CVE-2024-45863: Null dereference in Facebook Thrift

> Attackers can crash applications using Facebook Thrift by sending requests with invalid protocols, causing a null dereference.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Sep 2024
- **Updated:** 27 Sep 2024
- **Also known as:** GHSA-2wr3-8g8v-wc39

## What is CVE-2024-45863?

CVE-2024-45863 is a medium-severity vulnerability in Facebook Thrift, published on 27 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A null-dereference vulnerability involving parsing requests specifying invalid protocols can cause the application to crash or potentially result in other undesirable effects. This issue affects Facebook Thrift from v2024.09.09.00 until v2024.09.23.00.

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


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

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

## Is CVE-2024-45863 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-45863 is a medium-severity vulnerability in Facebook Thrift, published on 27 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-45863 in the wild and no public exploit code.

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

## Sources

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

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