cve.bz

CVE-2024-12289 hashicorp boundary: Improper Initialization

5.9 mediumEPSS 0.4%Fix available

Medium (5.9) in hashicorp boundary. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/hashicorp/boundary 0.18.2.

On this page
Boundary Community Edition and Boundary Enterprise (“Boundary”) incorrectly handle HTTP requests during the initialization of the Boundary controller, which may cause the Boundary server to terminate prematurely. Boundary is only vulnerable to this flaw during the initialization of the Boundary controller, which on average is measured in milliseconds during the Boundary startup process. This vulnerability, CVE-2024-12289, is fixed in Boundary Community Edition and Boundary Enterprise 0.16.4, 0.17.3, 0.18.2.

Severity

CVSS 3.1

5.9 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 34th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2024-12-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-665 Improper Initialization
CWE-460 Improper Cleanup on Thrown Exception
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-12289 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-12289?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-12289?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-12289 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
HashiCorp Boundaryfrom 0.8.0 before 0.18.2
HashiCorp Boundary Enterprisefrom 0.8.0 before 0.18.2

Fixed in

ProductFixed in
HashiCorp Boundary0.16.4
HashiCorp Boundary0.17.3
HashiCorp Boundary Enterprise0.16.4
HashiCorp Boundary Enterprise0.17.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-xx83-cxmq-x89mGogithub.com/hashicorp/boundary<0.18.20.18.2
GO-2024-3335Gogithub.com/hashicorp/boundary<0.18.20.18.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
openSUSETumbleweedgovulncheck-vulndb0.0.20241218T202206-1.1openSUSE-SU-2024:14603-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON