Legacy Node API Allows Impersonation in github.com/spiffe/spire/pkg/server/endpoints/node
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/spiffe/spire Go |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| github.com/spiffe/spire Go |
|
|
0.11.30.12.1In 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 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.
From the CVE record · mitre
Specially crafted requests to SPIRE Server’s Legacy Node API FetchX509SVID RPC can cause issuance of an X.509 certificate for a SPIFFE ID the agent is not authorized to distribute. The caller must present a valid agent certificate authorized to issue at least one SPIFFE ID, and the requested ID must belong to the same trust domain.
Check deployments using Go package github.com/spiffe/spire versions >=0.8.1 <0.8.5, >=0.9.0 <0.9.4, >=0.10.0 <0.10.2, >=0.11.0 <0.11.3, or >=0.12.0 <0.12.1.