Skip to content
Fencer Intel
medium 5.3

CVE-2022-3920 json

Consul Peering Imported Nodes/Services Leak

published 3y ago modified 2mo ago also BIT-consul-2022-3920 , EUVD-2022-7353 , GHSA-gw2g-hhc9-wgjh , GO-2022-1121

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 54%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/hashicorp/consul 1.14.0
  • bitnami consul 1.13.4
  • consul Alpine 3.18, Alpine 3.17 1.14.1-r0

alpine advisories ALPINE-CVE-2022-3920

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2022-3920 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-3920 updated cvss 7.5

consul: Consul Cluster Peering Leaks Imported Nodes/Services Information

  • Red Hat Logging Subsystem for Red Hat OpenShift openshift-logging/logging-loki-rhel8 Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/acm-grafana-rhel8, rhacm2/cluster-curator-controller-rhel8, rhacm2/managedcluster-import-controller-rhel8 Red Hat OpenShift Container Platform 4 openshift4/ose-grafana, openshift4/topology-aware-lifecycle-manager-rhel8-operator Red Hat Openshift Data Foundation 4 odf4/odr-rhel8-operator, odf4/odf-multicluster-rhel9-operator
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.72% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/hashicorp/consul
>=1.13.0, <1.14.0
1.14.0
bitnami consul
>=1.13.0, <1.13.4
1.13.4

Affected products

  • HashiCorp Consul
  • HashiCorp Consul Enterprise

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.