| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/spiffe/spire | ≥ 0.10.0, < 0.10.2≥ 0.11.0, < 0.11.3≥ 0.12.0, < 0.12.1≥ 0.8.1, < 0.8.5≥ 0.9.0, < 0.9.4 | 0.10.20.11.30.12.10.8.50.9.4 |
| spire | ≥ 0.10.0, < 0.10.2≥ 0.11.0, < 0.11.3≥ 0.12.0, < 0.12.1≥ 0.8.1, ≤ 0.8.4≥ 0.9.0, < 0.9.4 | 0.10.20.11.30.12.10.9.4 |
In SPIRE 0.8.1 through 0.8.4 and before versions 0.9.4, 0.10.2, 0.11.3 and 0.12.1, specially crafted requests to the FetchX509SVID RPC of SPIRE Server’s Legacy Node API (github.com/spiffe/spire/pkg/server/endpoints/node) can result in the possible issuance of an X.509 certificate with a URI SAN for a SPIFFE ID that the agent is not authorized to distribute. Proper controls are in place to require that the caller presents a valid agent certificate that is already authorized to issue at least one SPIFFE ID, and the requested SPIFFE ID belongs to the same trust domain, prior to being able to trigger this vulnerability. This issue has been fixed in SPIRE versions 0.8.5, 0.9.4, 0.10.2, 0.11.3 and 0.12.1.
The changes introduced to address this issue are related to enforcing that the FetchX509SVID RPC of SPIRE Server’s Legacy Node API only issues X.509 certificates with SPIFFE IDs that the agent is authorized to distribute.
The patched version also includes a back-ported change that improves the handling of file descriptors related to workload attestation in SPIRE Agent.
There are no changes in the expected behavior of SPIRE.
All SPIRE users running affected versions are advised to upgrade to the corresponding patched version.
No workarounds have been identified for this vulnerability.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free