github.com/hashicorp/boundary vulnerabilities
- Registry
- Go
- Latest
- 0.21.3
9 known advisories
The latest version, 0.21.3, is not affected by any of them. Projects on older versions may be.
go get github.com/hashicorp/boundary@v0.21.3Is your project on an affected github.com/hashicorp/boundary?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for github.com/hashicorp/boundary
Hashicorp Boundary workers are vulnerable to a denial-of-service condition during node enrollment TLS handshakes in github.com/hashicorp/boundary
- Affected
- <0.19.5 · >=0.20.0 <0.20.3 · >=0.21.0 <0.21.3
- Fixed in
- 0.19.5, 0.20.3, 0.21.3
Hashicorp Boundary workers are vulnerable to a denial-of-service condition during node enrollment TLS handshakes
- Affected
- <0.19.5 · >=0.20.0 <0.20.3 · >=0.21.0 <0.21.3
- Fixed in
- 0.19.5, 0.20.3, 0.21.3
Boundary Community Edition Incorrectly Handles HTTP Requests On Initialization Which May Lead to a Denial of Service in github.com/hashicorp/boundary
- Affected
- <0.18.2
- Fixed in
- 0.18.2
Boundary Community Edition Incorrectly Handles HTTP Requests On Initialization Which May Lead to a Denial of Service
- Affected
- <0.18.2
- Fixed in
- 0.18.2
HashiCorp Boundary Workers Store Rotated Credentials in Plaintext Even When Key Management Service Configured in github.com/hashicorp/boundary
- Affected
- >=0.10.0 <0.12.0
- Fixed in
- 0.12.0
Boundary vulnerable to session hijacking through TLS certificate tampering in github.com/hashicorp/boundary
- Affected
- >=0.8.0 <0.15.0
- Fixed in
- 0.15.0
Boundary vulnerable to session hijacking through TLS certificate tampering
- Affected
- >=0.8.0 <0.15.0
- Fixed in
- 0.15.0
HashiCorp Boundary Workers Store Rotated Credentials in Plaintext Even When Key Management Service Configured
- Affected
- >=0.10.0 <0.12.0
- Fixed in
- 0.12.0
Hashicorp Boundary vulnerable to clickjacking
- Affected
- <=0.11.0
- Fixed in
- No fix released
Is your github.com/hashicorp/boundary version vulnerable?
- github.com/hashicorp/boundary 0.21No known advisories in 0.21.3
- github.com/hashicorp/boundary 0.20No known advisories in 0.20.3
- github.com/hashicorp/boundary 0.19No known advisories in 0.19.5
- github.com/hashicorp/boundary 0.182 advisories in 0.18.2
- github.com/hashicorp/boundary 0.174 advisories in 0.17.2
- github.com/hashicorp/boundary 0.164 advisories in 0.16.3
Which of your client projects still run an old github.com/hashicorp/boundary?
NPMscan reads the go.mod in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Go packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Go registry.