Skip to content
Fencer Intel
high —

GHSA-m7vp-hqwv-7m5x json

Unbounded memory usage on exposed HTTP/2 (non-gRPC) endpoints

published 4y ago modified 2mo ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Impact The net/http Go package has a reported vulnerability tracked under CVE-2021-44716 which allows attacker controlled HTTP/2 requests to trigger unbounded memory usage in HTTP/2 endpoints. gRPC endpoints are not vulnerable as they rely on their own HTTP/2 implementation instead of the net/http package. HTTP/2 endpoints consuming the net/http package within SPIRE server and agent (or other components in this repository) that are _on by default_ include the following: - OIDC Discovery Provider - K8s Workload Registrar in webhook mode

The following endpoints are vulnerable _when enabled_: - SPIRE server bundle endpoint (i.e. Federation API)

The following endpoints are _NOT_ vulnerable, since HTTP/2 support in go is not enabled on non-TLS protected endpoints: - SPIRE server/agent metrics endpoint when configured for Prometheus - SPIRE server/agent health endpoints - SPIRE server/agent profiling endpoints

### Patches SPIRE 1.0.3 and 1.1.3 have been released with an upgraded Go toolchain which patches the vulnerability

### Workarounds The vulnerability can be worked around entirely by including the `http2server=0` value in the `GODEBUG` environment variable (see https://github.com/golang/go/issues/50058). This turns off HTTP/2 support on all non-gRPC endpoints. They will still function with HTTP/1.1.

The risk associated with this vulnerability can be somewhat mitigated by limiting the exposure of the endpoints in question. If necessary, vulnerable components or endpoints that are optionally configured can be disabled temporarily.

### References - https://github.com/golang/go/issues/50058 - https://go-review.googlesource.com/c/go/+/370574/ - https://nvd.nist.gov/vuln/detail/CVE-2021-44716

Patch / fix

  • go github.com/spiffe/spire 1.0.3, 1.1.3

Is GHSA-m7vp-hqwv-7m5x 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

Affected packages

ecosystem package affected fixed in
go github.com/spiffe/spire
<1.0.3
>=1.1.0, <1.1.3
1.0.3
1.1.3

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.