# CVE-2022-29077: Memory corruption in n/a

> Attackers can trigger a heap-based buffer overflow in rippled to execute remote commands or crash the node, threatening XRPL network stability and assets.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 25 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-cgf8-qv4v-rpfv

## What is CVE-2022-29077?

CVE-2022-29077 is a critical memory corruption vulnerability in n/a, published on 25 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A heap-based buffer overflow exists in rippled before 1.8.5. The vulnerability allows attackers to cause a crash or execute commands remotely on a rippled node, which may lead to XRPL mainnet DoS or compromise. This exposes all digital assets on the XRPL to a security threat.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2022-29077?

It affects 1 product.


Products: Ripple Rippled.

## How do I fix CVE-2022-29077?

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

## Is CVE-2022-29077 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-29077 and fix it if it is affected.

What it is: CVE-2022-29077 is a critical memory corruption vulnerability in n/a, published on 25 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-29077 in the wild and no public exploit code.

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

## Sources

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

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