Skip to content
Fencer Intel
high 8.1

CVE-2021-27098 json

Legacy Node API Allows Impersonation in github.com/spiffe/spire/pkg/server/endpoints/node

published 5y ago modified 4mo ago also GHSA-h746-rm5q-8mgq , EUVD-2021-1097

cvss
8.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 46%
public exploits
0
none known

Summary

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 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.

Patch / fix

  • go github.com/spiffe/spire 0.8.5, 0.9.4, 0.10.2, 0.11.3, 0.12.1
  • cncf spire 0.9.4, 0.10.2, 0.11.3, 0.12.1

Is CVE-2021-27098 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

Exploit prediction

0.56% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
NVD 2.0 5.5 AV:N/AC:L/Au:S/C:P/I:P/A:N
GitHub 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/spiffe/spire
>=0.8.1, <0.8.5
>=0.9.0, <0.9.4
>=0.10.0, <0.10.2
>=0.11.0, <0.11.3
>=0.12.0, <0.12.1
0.8.5
0.9.4
0.10.2
0.11.3
0.12.1

Classification

Weakness
  • CWE-295 Improper Certificate Validation
  • CWE-284 Improper Access Control

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.