# CVE-2024-53379: Memory corruption in n/a

> A remote attacker can cause a denial of service in SharkSSL by sending a malformed Client-Hello message, triggering a heap buffer overflow.

- **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:** No
- **Published:** 23 Jan 2025
- **Updated:** 27 Feb 2025
- **Also known as:** GHSA-2p6v-g3wm-x2qp

## What is CVE-2024-53379?

CVE-2024-53379 is a high-severity memory corruption vulnerability in n/a, published on 23 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Heap buffer overflow in the server site handshake implementation in Real Time Logic LLC's SharkSSL version (from 05/05/24) commit 64808a5e12c83b38f85c943dee0112e428dc2a43 allows a remote attacker to trigger a Denial-of-Service via a malformed Client-Hello message.

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

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


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

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

## Is CVE-2024-53379 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-53379 is a high-severity memory corruption vulnerability in n/a, published on 23 Jan 2025. 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-53379 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-53379/ (Markdown: https://insights.sbomify.com/CVE-2024-53379/index.md)
```

## Sources

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

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