Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CVE-2022-30324 Nomad Impacted by go-getter Vulnerabilities #13057

Closed
mmcquillan opened this issue May 18, 2022 · 2 comments
Closed

CVE-2022-30324 Nomad Impacted by go-getter Vulnerabilities #13057

mmcquillan opened this issue May 18, 2022 · 2 comments

Comments

@mmcquillan
Copy link
Collaborator

mmcquillan commented May 18, 2022

Summary

A vulnerability was identified in the go-getter library that Nomad and Nomad Enterprise (“Nomad”) uses for its artifacts such that a specially crafted Nomad jobspec can be used for privilege escalation onto client agent hosts. This vulnerability affects Nomad versions 0.2.0 through 1.3.0, and is fixed in the 1.1.14, 1.2.8, and 1.3.1 releases.

Background

Nomad utilizes HashiCorp’s go-getter library for its artifact stanza that can be included in jobs submitted to the cluster. These custom artifacts (files) can be retrieved using various protocols.

Details

Vulnerabilities were discovered externally and internally affecting the go-getter library (CVE-2022-26945, CVE-2022-30321, CVE-2022-30322, CVE-2022-30323). Nomad uses this library directly for its artifact stanza. The vulnerabilities can lead to Nomad operators with the ability to submit specially crafted jobspecs to be able to escalate privileges onto client agent hosts. This issue is identified publicly as CVE-2022-30324.

Remediation

Customers should upgrade to Nomad or Nomad Enterprise 1.1.14, 1.2.8, 1.3.1, or newer. Please refer to Upgrading Nomad for general guidance and version-specific upgrade notes.

@lgfa29 lgfa29 removed the type/bug label May 20, 2022
@lgfa29 lgfa29 changed the title placeholder CVE-2022-30324 Nomad Impacted by go-getter Vulnerabilities May 20, 2022
@lgfa29 lgfa29 closed this as completed May 20, 2022
@tgross
Copy link
Member

tgross commented Jul 5, 2022

ref 3968509

@github-actions
Copy link

github-actions bot commented Nov 3, 2022

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants