# CVE-2019-13000: Missing authorization in n/a

> Attackers can trigger loss of funds in the Eclair Lightning client due to incorrect access control mechanisms.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-7q9j-f2wq-66jx

## What is CVE-2019-13000?

CVE-2019-13000 is a high-severity missing authorization vulnerability in n/a, published on 31 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Eclair through 0.3 allows attackers to trigger loss of funds because of Incorrect Access Control. NOTE: README.md states "it is beta-quality software and don't put too much money in it."

## Which versions are affected by CVE-2019-13000?

It affects 1 product.


Products: Acinq Eclair.

## How do I fix CVE-2019-13000?

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

## Is CVE-2019-13000 being exploited?

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

Public exploit code:

- A tool that detect if your node has been victim of the invalid funding tx attack. (github_poc): https://github.com/ACINQ/detection-tool-cve-2019-13000

## Other vulnerabilities in n/a

- [CVE-2021-41591](https://insights.sbomify.com/CVE-2021-41591/): Business logic in n/a (critical 9.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-13000 and fix it if it is affected.

What it is: CVE-2019-13000 is a high-severity missing authorization vulnerability in n/a, published on 31 Jan 2020. 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-2019-13000 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-2019-13000/ (Markdown: https://insights.sbomify.com/CVE-2019-13000/index.md)
```

## Sources

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

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