# CVE-2021-41593: Business logic in n/a

> Attackers can cause loss of funds in the Lightning Network daemon due to improper handling of dust HTLCs.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Oct 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-gjfm-mwrf-wg3p

## What is CVE-2021-41593?

CVE-2021-41593 is a high-severity vulnerability in n/a, published on 4 Oct 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Lightning Labs lnd before 0.13.3-beta allows loss of funds because of dust HTLC exposure.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2021-41593?

It affects 1 product.


Products: Lightning Network Daemon Project Lightning Network Daemon.

## How do I fix CVE-2021-41593?

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

## Is CVE-2021-41593 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-26896](https://insights.sbomify.com/CVE-2020-26896/): Business logic in n/a (high 8.2)
- [CVE-2020-26895](https://insights.sbomify.com/CVE-2020-26895/): Business logic in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-41593 and fix it if it is affected.

What it is: CVE-2021-41593 is a high-severity vulnerability in n/a, published on 4 Oct 2021. 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-2021-41593 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-2021-41593/ (Markdown: https://insights.sbomify.com/CVE-2021-41593/index.md)
```

## Sources

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

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