Skip to content

GHSA-2w2v-xcr9-mj4m CVE-2019-12618 GO-2023-1928

Hashicorp Nomad Access Control Issues

Critical Go
Severity
9.8 / 10
Critical · CVSS 3.0
Exploit chance (EPSS)
2.42%
Chance of exploitation in the next 30 days. Higher than 84.18% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-269 Improper Privilege Management
Fix
0.9.2
Upgrade github.com/hashicorp/nomad to this version or later

Description

HashiCorp Nomad 0.9.0 through 0.9.1 has Incorrect Access Control via the exec driver.

Affected versions

Go

PackageVulnerableFixed in
github.com/hashicorp/nomad
>= 0.9.0, < 0.9.2
0.9.2

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

github.com/hashicorp/nomad Go → 0.9.2

go
go get github.com/hashicorp/nomad@v0.9.2 && go mod tidy

Severity breakdown

CVSS 3.0 9.8

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-269: Improper Privilege Management

The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.

How to prevent it
  • Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • Architecture and Design: Follow the principle of least privilege when assigning access rights to entities in a software system.
  • Architecture and Design: Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-hx53-77qj-8663
HashiCorp Nomad vulnerable to a path traversal
High Also affects github.com/hashicorp/nomad
GHSA-3934-423w-4jq3
HashiCorp Nomad vulnerable to symlink attack
Medium Also affects github.com/hashicorp/nomad
GHSA-rx97-6c62-55mf
Hashicorp Nomad Incorrect Privilege Assignment vulnerability
High Also affects github.com/hashicorp/nomad
GHSA-c3q9-q986-vrwh
Nomad is vulnerable to unintentional exposure of the workload identity token and client secret token in audit logs
Medium Also affects github.com/hashicorp/nomad
GHSA-hr68-hvgv-xxqf
Hashicorp Nomad Incorrect Privilege Assignment vulnerability
Medium Also affects github.com/hashicorp/nomad
GHSA-2w5v-x29g-jw7j
Hashicorp Nomad Incorrect Authorization vulnerability
High Also affects github.com/hashicorp/nomad
GHSA-25qx-vfw2-fw8r
Nomad Vulnerable to Allocation Directory Escape On Non-Existing File Paths Through Archive Unpacking
Medium Also affects github.com/hashicorp/nomad
GHSA-5mqx-rpxv-mvxj
HashiCorp Nomad is vulnerable to path escape through archive unpacking during migration
High Also affects github.com/hashicorp/nomad
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor