Skip to content
Fencer Intel
medium 5.9

CVE-2024-12289 json

Boundary Controller Incorrectly Handles HTTP Requests On Initialization Which May Lead to a Denial of Service

published last yr. modified 4mo ago also EUVD-2024-3526 , GHSA-xx83-cxmq-x89m , GO-2024-3335

cvss
5.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 34%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/hashicorp/boundary 0.18.2
  • HashiCorp Boundary 0.16.4, 0.17.3, 0.18.2
  • HashiCorp Boundary Enterprise 0.16.4, 0.17.3, 0.18.2
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20241218T202206-1.1

opensuse advisories openSUSE-SU-2024:14603-1

Is CVE-2024-12289 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.39% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-15).

CVSS scores

assigned by version score vector
CNA 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
go github.com/hashicorp/boundary
<0.18.2
0.18.2

Affected products

  • HashiCorp Boundary
  • HashiCorp Boundary Enterprise

Classification

Weakness
  • CWE-460 Improper Cleanup on Thrown Exception
  • CWE-665 Improper Initialization

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.