# CVE-2019-12999: Improper Access Control in Lightning Network Daemon

> Attackers can trigger loss of funds in Lightning Network Daemon due to incorrect access control, requiring an upgrade to secure assets.

- **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:** Yes
- **Published:** 31 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-78hj-86cr-6j2v, GO-2022-0807

## What is CVE-2019-12999?

CVE-2019-12999 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

Lightning Network Daemon (lnd) before 0.7 allows attackers to trigger loss of funds because of Incorrect Access Control.

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

3 open source packages ship an affected version, including github.com/lightningnetwork/lnd. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/lightningnetwork/lnd` | Go | All versions | 0.7.1-beta |
| `github.com/lightningnetwork/lnd` | Go | All versions | 0.7.1-beta |
| `github.com/lightningnetwork/lnd` | Go | All versions | 0.7.1-beta |

Products: Lightning Network Daemon.

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

Upgrade github.com/lightningnetwork/lnd to 0.7.1-beta or later.

## Is CVE-2019-12999 being exploited?

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

Public exploit code:

- A tool to check if your lnd node was targeted by CVE-2019-12999 (github_poc): https://github.com/lightninglabs/chanleakcheck

## Fix prompt for AI coding agents

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

What it is: CVE-2019-12999 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-12999 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/lightningnetwork/lnd (Go): affected all versions; fixed in 0.7.1-beta
- github.com/lightningnetwork/lnd (Go): affected all versions; fixed in 0.7.1-beta
- github.com/lightningnetwork/lnd (Go): affected all versions; fixed in 0.7.1-beta

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

## Sources

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

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