CVE-2023-1782
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedHashiCorp Nomad and Nomad Enterprise versions 1.5.0 up to 1.5.2 allow unauthenticated users to bypass intended ACL authorizations for clusters where mTLS is not enabled. This issue is fixed in version 1.5.3.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceHashiCorp Nomad versions 1.5.0-1.5.2 contain an ACL authorization bypass vulnerability allowing unauthenticated users to access protected resources when mTLS is not enabled on the cluster, due to insufficient access control validation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 1.5.0, <= 1.5.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed Nomad versionRun `nomad version` on any Nomad client or server node to retrieve the version string.Affected if version output shows 1.5.0, 1.5.1, or 1.5.2
-
Locate Nomad configuration filesCheck for configuration files in default locations: `/etc/nomad.d/nomad.hcl`, `/etc/nomad.hcl`, or the file specified via `-config` flag when starting the Nomad agent.Affected if configuration file exists and can be inspected
-
Verify if mTLS is configured in NomadExamine the Nomad configuration file for TLS-related settings. Look for a `tls` block containing `enabled = true`, or settings such as `ca_file`, `cert_file`, `key_file`, or `verify_https_client` being set.Affected if no `tls` block with `enabled = true` is present, or TLS certificate settings are absent/undefined, meaning mTLS is disabled or not configured
Affected if Nomad version is 1.5.0, 1.5.1, or 1.5.2 AND mTLS is not enabled in the configuration (the vulnerable condition is the absence of mTLS protection).
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedEnable mTLS for Nomad cluster communications or upgrade to version 1.5.3 or later.
1.5.3
- Plan an upgrade to Nomad version 1.5.3 or later
- Test the upgrade in a non-production environment first
- Back up your Nomad data and configuration files
- Upgrade Nomad to version 1.5.3 following the official HashiCorp upgrade documentation
- After upgrade, verify that ACL authorization is functioning correctly
- If mTLS was not previously enabled, consider enabling it for enhanced security
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1782 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-1782 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data