Hashicorp Nomad/Nomad Enterprise up to 1.0.17/1.1.11/1.2.5 information disclosure

Summaryinfo

A vulnerability marked as problematic has been reported in Hashicorp Nomad and Nomad Enterprise up to 1.0.17/1.1.11/1.2.5. The affected element is an unknown function. This manipulation causes information disclosure. The identification of this vulnerability is CVE-2022-24683. There is no exploit available.

Detailsinfo

A vulnerability was found in Hashicorp Nomad and Nomad Enterprise up to 1.0.17/1.1.11/1.2.5. It has been declared as problematic. Affected by this vulnerability is an unknown code. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality.

The weakness was shared 02/18/2022. The advisory is shared at discuss.hashicorp.com. This vulnerability is known as CVE-2022-24683 since 02/09/2022. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Hashicorp

Name

• Nomad
• Nomad Enterprise

Version

• 1.0.0
• 1.0.1
• 1.0.2
• 1.0.3
• 1.0.4
• 1.0.5
• 1.0.6
• 1.0.7
• 1.0.8
• 1.0.9
• 1.0.10
• 1.0.11
• 1.0.12
• 1.0.13
• 1.0.14
• 1.0.15
• 1.0.16
• 1.0.17
• 1.1.0
• 1.1.1
• 1.1.2
• 1.1.3
• 1.1.4
• 1.1.5
• 1.1.6
• 1.1.7
• 1.1.8
• 1.1.9
• 1.1.10
• 1.1.11
• 1.2.0
• 1.2.1
• 1.2.2
• 1.2.3
• 1.2.4
• 1.2.5

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion