# CVE-2022-3920: Consul Peering Imported Nodes/Services Leak

> Attackers can view imported nodes and services via UI endpoints in Consul peering configurations, exposing internal topology details.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 15 Nov 2022
- **Updated:** 29 Apr 2025
- **Also known as:** BIT-consul-2022-3920, GHSA-gw2g-hhc9-wgjh, GO-2022-1121, UBUNTU-CVE-2022-3920

## What is CVE-2022-3920?

CVE-2022-3920 is a medium-severity vulnerability in HashiCorp Consul, published on 15 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HashiCorp Consul and Consul Enterprise 1.13.0 up to 1.13.3 do not filter cluster filtering's imported nodes and services for HTTP or RPC endpoints used by the UI. Fixed in 1.14.0.

Weakness: CWE-862 (Missing Authorization)

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

4 open source packages ship an affected version, including github.com/hashicorp/consul and consul. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/hashicorp/consul` | Go | From 1.13.0 | 1.14.0 |
| `github.com/hashicorp/consul` | Go | From 1.13.0 | 1.14.0 |
| `github.com/hashicorp/consul` | Go | From 1.13.0 | 1.14.0 |
| `consul` | Bitnami | From 1.13.0 | 1.13.4 |

Products: Hashicorp Consul.

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

Upgrade github.com/hashicorp/consul to 1.14.0 or later.

## Is CVE-2022-3920 being exploited?

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

## Other vulnerabilities in HashiCorp Consul

- [CVE-2021-41805](https://insights.sbomify.com/CVE-2021-41805/): Privilege escalation in n/a (high 8.8)
- [CVE-2021-37219](https://insights.sbomify.com/CVE-2021-37219/): HashiCorp Consul Privilege Escalation Vulnerability (high 8.8)
- [CVE-2023-2816](https://insights.sbomify.com/CVE-2023-2816/): Consul Envoy Extension Downsteam Proxy Configuration By Upstream Service Owner (high 8.7)
- [CVE-2024-10006](https://insights.sbomify.com/CVE-2024-10006/): Consul L7 Intentions Vulnerable To Headers Bypass (high 8.3)
- [CVE-2024-10005](https://insights.sbomify.com/CVE-2024-10005/): Consul L7 Intentions Vulnerable To URL Path Bypass (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3920 is a medium-severity vulnerability in HashiCorp Consul, published on 15 Nov 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-3920 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/hashicorp/consul (Go): affected from 1.13.0; fixed in 1.14.0
- github.com/hashicorp/consul (Go): affected from 1.13.0; fixed in 1.14.0
- github.com/hashicorp/consul (Go): affected from 1.13.0; fixed in 1.14.0
- consul (Bitnami): affected from 1.13.0; fixed in 1.13.4

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

## Sources

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

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