# CVE-2022-35913: Denial of service in n/a

> An attacker can prevent a victim from completing a Stonewallx2 transaction by racing to broadcast a conflicting transaction with lower fees.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-vg6m-6qgh-29qp

## What is CVE-2022-35913?

CVE-2022-35913 is a medium-severity denial of service vulnerability in n/a, published on 6 Sep 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Samourai Wallet Stonewallx2 0.99.98e allows a denial of service via a P2P coinjoin. The attacker and victim must follow each other's paynym. Then, the victim must try to collaborate with the attacker for a Stonewallx2 transaction. Next, the attacker broadcasts a tx, spending the inputs used in Stonewallx2 before the victim can broadcast the collaborative transaction. The attacker does not signal opt in RBF, and uses the lowest fee rate. This would result in the victim being unable to perform Stonewallx2. (Note that the attacker could use multiple paynyms.)

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Kayako Samourai.

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

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

## Is CVE-2022-35913 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-35913 is a medium-severity denial of service vulnerability in n/a, published on 6 Sep 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-35913 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-35913/ (Markdown: https://insights.sbomify.com/CVE-2022-35913/index.md)
```

## Sources

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

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