# CVE-2024-48425: Null dereference in n/a

> A null pointer dereference in the Assimp library allows attackers to cause a denial of service via crafted 3D model files.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Oct 2024
- **Updated:** 28 Oct 2024
- **Also known as:** DEBIAN-CVE-2024-48425, GHSA-5qr5-9jfv-96j2, OESA-2024-2360, PYSEC-2024-293, UBUNTU-CVE-2024-48425

## What is CVE-2024-48425?

CVE-2024-48425 is a medium-severity vulnerability in n/a, published on 24 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A segmentation fault (SEGV) was detected in the Assimp::SplitLargeMeshesProcess_Triangle::UpdateNode function within the Assimp library during fuzz testing using AddressSanitizer. The crash occurs due to a read access violation at address 0x000000000460, which points to the zero page, indicating a null or invalid pointer dereference.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

1 open source package ship an affected version, including pyassimp. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pyassimp` | PyPI | All versions to 5.4.3 | None |

Products: Assimp Assimp.

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

Upgrade to a fixed version.

## Is CVE-2024-48425 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-45748](https://insights.sbomify.com/CVE-2022-45748/): Use after free in n/a (high 8.8)
- [CVE-2024-48423](https://insights.sbomify.com/CVE-2024-48423/): Use after free in n/a (high 8.4)
- [CVE-2024-45679](https://insights.sbomify.com/CVE-2024-45679/): Memory corruption in Assimp (high 8.4)
- [CVE-2024-40724](https://insights.sbomify.com/CVE-2024-40724/): Memory corruption in Assimp (high 8.4)
- [CVE-2022-38528](https://insights.sbomify.com/CVE-2022-38528/): Null dereference in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-48425 is a medium-severity vulnerability in n/a, published on 24 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48425 exists.

Affected packages and fixed versions:
- pyassimp (PyPI): affected all versions up to 5.4.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-48425/ (Markdown: https://insights.sbomify.com/CVE-2024-48425/index.md)
```

## Sources

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

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