# CVE-2024-53432: Denial of service in n/a

> Attackers can cause a denial of service by providing malformed PLY files to applications using the Point Cloud Library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Nov 2024
- **Updated:** 4 Dec 2024
- **Also known as:** DEBIAN-CVE-2024-53432, GHSA-6q3r-569c-crm7, UBUNTU-CVE-2024-53432, USN-7227-1

## What is CVE-2024-53432?

CVE-2024-53432 is a high-severity denial of service vulnerability in n/a, published on 21 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

While parsing certain malformed PLY files, PCL version 1.14.1 crashes due to an uncaught std::out_of_range exception in PCLPointCloud2::at. This issue could potentially be exploited to cause a denial-of-service (DoS) attack when processing untrusted PLY files.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

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


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

Apply the vendor's patch.

## Is CVE-2024-53432 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-53432 is a high-severity denial of service vulnerability in n/a, published on 21 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-53432 exists.

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

## Sources

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

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