Vulnerability in github.com/hashicorp/vault (CVE-2023-4680)
Summary
Vulnerability in github.com/hashicorp/vault (CVE-2023-4680). Confidential information can be exposed externally. Mitigation: upgrade to 1.12.11, 1.13.7, 1.14.3 or later.
Original description
The description as published by the source.
HashiCorp Vault and Vault Enterprise transit secrets engine allowed authorized users to specify arbitrary nonces, even with convergent encryption disabled. The encrypt endpoint, in combination with an offline attack, could be used to decrypt arbitrary ciphertext and potentially derive the authentication subkey when using transit secrets engine without convergent encryption. Introduced in 1.6.0 and fixed in 1.14.3, 1.13.7, and 1.12.11.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A weakness called CVE-2023-4680 was discovered in github.com/hashicorp/vault.
In plain terms, it is improper input validation.
Severity is Info. Low severity or not yet rated.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "github.com/hashicorp/vault CVE-2023-4680".
CVE-2023-4680 (github.com/hashicorp/vault). Severity: Info. Category: CWE-20.
Response plan:
- Check the vendor advisory for affected versions and the patched release.
- If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
- If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
- Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.
A weakness (CVE-2023-4680) in github.com/hashicorp/vault. In plain words, it is improper input validation.
Target versions of github.com/hashicorp/vault (see vendor advisory). If running in production, identify exposure immediately.
Severity: Info. Low severity or not yet rated.
Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-20)
If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.
Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.
Affected packages
References
- advisory discuss.hashicorp.com
- advisory github.com
- package github.com
- web nvd.nist.gov