CVE-2022-3867 json
Nomad Event Stream Subscriber Using a Token with TTL Receives Updates Until Garbage Collected
published 3y ago modified 4mo ago also GHSA-9fmc-5fq4-5jwh , GO-2022-1106 , EUVD-2022-7302
- cvss
- 2.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 47%
- public exploits
- 0
- none known
Summary
HashiCorp Nomad and Nomad Enterprise 1.4.0 up to 1.4.1 event stream subscribers using a token with TTL receive updates until token garbage is collected. Fixed in 1.4.2.
Patch / fix
Is CVE-2022-3867 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.57% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 2.7 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N |
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| GitHub | 3.1 | 2.7 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/hashicorp/nomad | >=1.4.0, <1.4.2 |
1.4.2 |
Affected products
- HashiCorp Nomad
- HashiCorp Nomad Enterprise
Classification
- Weakness
-
- CWE-613 DEPRECATED: Insufficient Session Expiration
References
-
github.com
/hashicorp/nomad/commit/dd6a4634a9652197fe4182e830f9a737d0ae1216
web, patch
-
discuss.hashicorp.com
/t/hcsec-2022-26-nomad-s-event-stream-subscriber-using-acl-token-with-ttl-receive-updates-until-garbage-collec
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-3867
advisory
-
github.com
/hashicorp/nomad
package
-
github.com
/advisories/GHSA-9fmc-5fq4-5jwh
advisory
Sources
- CVE List CVE-2022-3867
- GitHub Advisory GHSA-9fmc-5fq4-5jwh
- NVD CVE-2022-3867
- OSV GO-2022-1106
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.