# CVE-2023-3299: Nomad Caller ACL Token's Secret ID is Exposed to Sentinel

> Attackers can expose ACL token secret IDs to Sentinel due to a policy parsing error in HashiCorp Nomad Enterprise.

- **Severity:** Low 3.4 (`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jul 2023
- **Updated:** 17 Oct 2024
- **Also known as:** GHSA-9jfx-84v9-2rr2, GO-2024-2669, UBUNTU-CVE-2023-3299

## What is CVE-2023-3299?

CVE-2023-3299 is a low-severity vulnerability in HashiCorp Nomad Enterprise, published on 19 Jul 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

HashiCorp Nomad Enterprise 1.2.11 up to 1.5.6, and 1.4.10 ACL policies using a block without a label generates unexpected results. Fixed in 1.6.0, 1.5.7, and 1.4.11.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere), CWE-201 (Insertion of Sensitive Information Into Sent Data)

## Which versions are affected by CVE-2023-3299?

5 open source packages ship an affected version, including github.com/hashicorp/nomad. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/hashicorp/nomad` | Go | From 1.2.11 | 1.4.11, 1.5.7 |
| `github.com/hashicorp/nomad` | Go | From 1.2.11 | 1.4.11 |
| `github.com/hashicorp/nomad` | Go | From 1.2.11 | 1.4.11 |
| `github.com/hashicorp/nomad` | Go | From 1.5.0 | 1.5.7 |
| `github.com/hashicorp/nomad` | Go | From 1.5.0 | 1.5.7 |

Products: Hashicorp Nomad.

## How do I fix CVE-2023-3299?

Upgrade github.com/hashicorp/nomad to a fixed version for your release line: 1.4.11 or 1.5.7.

## Is CVE-2023-3299 being exploited?

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

## Other vulnerabilities in HashiCorp Nomad Enterprise

- [CVE-2023-1782](https://insights.sbomify.com/CVE-2023-1782/): Nomad Unauthenticated Client Agent HTTP Request Privilege Escalation (critical 10.0)
- [CVE-2022-30324](https://insights.sbomify.com/CVE-2022-30324/): Privilege escalation in Hashicorp Nomad (critical 9.8)
- [CVE-2020-7956](https://insights.sbomify.com/CVE-2020-7956/): Improper Certificate Validation in HashiCorp Nomad (critical 9.8)
- [CVE-2019-12618](https://insights.sbomify.com/CVE-2019-12618/): Hashicorp Nomad Access Control Issues (critical 9.8)
- [CVE-2020-27195](https://insights.sbomify.com/CVE-2020-27195/): Use After Free in HashiCorp Nomad (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-3299 and fix it if it is affected.

What it is: CVE-2023-3299 is a low-severity vulnerability in HashiCorp Nomad Enterprise, published on 19 Jul 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-3299 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/hashicorp/nomad (Go): affected from 1.2.11; fixed in 1.4.11, 1.5.7
- github.com/hashicorp/nomad (Go): affected from 1.2.11; fixed in 1.4.11
- github.com/hashicorp/nomad (Go): affected from 1.2.11; fixed in 1.4.11
- github.com/hashicorp/nomad (Go): affected from 1.5.0; fixed in 1.5.7
- github.com/hashicorp/nomad (Go): affected from 1.5.0; fixed in 1.5.7

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

## Sources

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

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