CVE-2023-24999: Vault Fails to Verify if the AppRole SecretID Belongs to Role During a Destroy Operation
Noroxi assessment
Priority: Monitor (action score 32/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.59% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: HashiCorp Vault 1.10.11, 1.11.8, 1.12.4; HashiCorp Vault Enterprise 1.10.11, 1.11.8, 1.12.4.
- Severity is disputed: the assigning authority (CNA) scores it 4.4, NVD 8.1.
Low priority for now. Upgrade to HashiCorp Vault 1.10.11, 1.11.8, 1.12.4; HashiCorp Vault Enterprise 1.10.11, 1.11.8, 1.12.4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
HashiCorp Vault and Vault Enterprise’s approle auth method allowed any authenticated user with access to an approle destroy endpoint to destroy the secret ID of any other role by providing the secret ID accessor. This vulnerability is fixed in Vault 1.13.0, 1.12.4, 1.11.8, 1.10.11 and above.
- Published
- Mar 10, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.5% · 49th percentile
- CWE
- CWE-863
Report tools
Action score
32
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 8.1
- CNA · HashiCorp
- 4.4
- 3.7 point gap
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| hashicorp | vault | cpe:2.3:a:hashicorp:vault |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (HashiCorp). Independent of NVD's CPE analysis and usually ahead of it.
HashiCorp Vault
- 1.12.0 and later · before 1.12.4affected · semver
- 1.11.0 and later · before 1.11.8affected · semver
- before 1.10.11affected · semver
HashiCorp Vault Enterprise
- 1.12.0 and later · before 1.12.4affected · semver
- 1.11.0 and later · before 1.11.8affected · semver
- before 1.10.11affected · semver
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- hashicorp vaultbefore 1.10.11
- hashicorp vault1.11.0 and later · before 1.11.8
- hashicorp vault1.12.0 and later · before 1.12.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/hashicorp/vault | from 1.11.0 · before 1.11.8 | 1.11.8 |
| Go | github.com/hashicorp/vault | from 1.12.0 · before 1.12.4 | 1.12.4 |
| Go | github.com/hashicorp/vault | before 1.10.11 | 1.10.11 |
Same product
hashicorp: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-35192The official vault docker images before 0.11.6 contain a blank password for a root user.40Plan
- CVE-2024-2048Vault Cert Auth Method Did Not Correctly Validate Non-CA Certificates39Monitor
- CVE-2020-12757HashiCorp Vault and Vault Enterprise 1.4.0 and 1.4.1, when configured with the GCP Secrets Engine, may incorrectly generate GCP Credentials…39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2022-40186Sep 21, 2022 · An issue was discovered in HashiCorp Vault and Vault Enterprise before 1.11.3.36Monitor
- ← EarlierCVE-2022-41316Oct 12, 2022 · HashiCorp Vault and Vault Enterprise’s TLS certificate auth method did not initially load the optionally configured CRL issued by the…21Monitor
- Later →CVE-2023-0620Mar 29, 2023 · Vault Vulnerable to SQL Injection When Configuring the Microsoft SQL Database Storage Backend26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| HashiCorp Vault | 1.10.11 | Vendor (CNA) |
| HashiCorp Vault | 1.11.8 | Vendor (CNA) |
| HashiCorp Vault | 1.12.4 | Vendor (CNA) |
| HashiCorp Vault Enterprise | 1.10.11 | Vendor (CNA) |
| HashiCorp Vault Enterprise | 1.11.8 | Vendor (CNA) |
| HashiCorp Vault Enterprise | 1.12.4 | Vendor (CNA) |
| Go:github.com/hashicorp/vault | 1.10.11 | Package registry (OSV) |
| Go:github.com/hashicorp/vault | 1.11.8 | Package registry (OSV) |
| Go:github.com/hashicorp/vault | 1.12.4 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.