CVE-2021-27099 (GCVE-0-2021-27099)

Vulnerability from cvelistv5 – Published: 2021-03-05 17:04 – Updated: 2024-08-03 20:40
VLAI?
Summary
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
Severity ?
No CVSS data available.
CWE
  • n/a
Assigner
References
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-03T20:40:47.281Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://github.com/spiffe/spire/security/advisories/GHSA-q7gm-mjrg-44h9"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "n/a",
          "vendor": "n/a",
          "versions": [
            {
              "status": "affected",
              "version": "n/a"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "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"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "n/a",
              "lang": "en",
              "type": "text"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2021-03-05T17:04:20",
        "orgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
        "shortName": "mitre"
      },
      "references": [
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/spiffe/spire/security/advisories/GHSA-q7gm-mjrg-44h9"
        }
      ],
      "x_legacyV4Record": {
        "CVE_data_meta": {
          "ASSIGNER": "cve@mitre.org",
          "ID": "CVE-2021-27099",
          "STATE": "PUBLIC"
        },
        "affects": {
          "vendor": {
            "vendor_data": [
              {
                "product": {
                  "product_data": [
                    {
                      "product_name": "n/a",
                      "version": {
                        "version_data": [
                          {
                            "version_value": "n/a"
                          }
                        ]
                      }
                    }
                  ]
                },
                "vendor_name": "n/a"
              }
            ]
          }
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "eng",
              "value": "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"
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "eng",
                  "value": "n/a"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://github.com/spiffe/spire/security/advisories/GHSA-q7gm-mjrg-44h9",
              "refsource": "MISC",
              "url": "https://github.com/spiffe/spire/security/advisories/GHSA-q7gm-mjrg-44h9"
            }
          ]
        }
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
    "assignerShortName": "mitre",
    "cveId": "CVE-2021-27099",
    "datePublished": "2021-03-05T17:04:20",
    "dateReserved": "2021-02-10T00:00:00",
    "dateUpdated": "2024-08-03T20:40:47.281Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "fkie_nvd": {
      "configurations": "[{\"nodes\": [{\"operator\": \"OR\", \"negate\": false, \"cpeMatch\": [{\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:cncf:spire:*:*:*:*:*:*:*:*\", \"versionEndExcluding\": \"0.8.5\", \"matchCriteriaId\": \"0CFBEF70-490C-49D7-B601-CE2C8ED7AC99\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:cncf:spire:*:*:*:*:*:*:*:*\", \"versionStartIncluding\": \"0.9.0\", \"versionEndExcluding\": \"0.9.4\", \"matchCriteriaId\": \"E7436751-C627-4143-A890-8B04D9C6642D\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:cncf:spire:*:*:*:*:*:*:*:*\", \"versionStartIncluding\": \"0.10.0\", \"versionEndExcluding\": \"0.10.2\", \"matchCriteriaId\": \"E330A728-6B22-4C71-B37A-119BD2D3EADB\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:cncf:spire:*:*:*:*:*:*:*:*\", \"versionStartIncluding\": \"0.11.0\", \"versionEndExcluding\": \"0.11.3\", \"matchCriteriaId\": \"EA57458D-53C5-4E8D-AFC2-D56826904304\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:cncf:spire:*:*:*:*:*:*:*:*\", \"versionStartIncluding\": \"0.12.0\", \"versionEndExcluding\": \"0.12.1\", \"matchCriteriaId\": \"F05F1090-6FFC-4C74-B9D3-D63B3259A46A\"}]}]}]",
      "descriptions": "[{\"lang\": \"en\", \"value\": \"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\"}, {\"lang\": \"es\", \"value\": \"En SPIRE versiones anteriores a 0.8.5, 0.9.4, 0.10.2, 0.11.3 y 0.12.1, el Node Attestor \\\"aws_iid\\\" normaliza inapropiadamente la ruta proporcionada por medio de la funcionalidad agent ID templating, lo que puede permitir la emisi\\u00f3n de un ID de SPIFFE dentro del mismo dominio confiable, si el atacante controla el valor de una etiqueta EC2 antes de una certificaci\\u00f3n, y el certificador est\\u00e1 configurado para plantillas de ID de agente donde el valor de la etiqueta es el \\u00faltimo elemento de la ruta.\u0026#xa0;Este problema ha sido corregido en versiones 0.11.3 y 0.12.1 de SPIRE\"}]",
      "id": "CVE-2021-27099",
      "lastModified": "2024-11-21T05:57:20.980",
      "metrics": "{\"cvssMetricV31\": [{\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"cvssData\": {\"version\": \"3.1\", \"vectorString\": \"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N\", \"baseScore\": 6.8, \"baseSeverity\": \"MEDIUM\", \"attackVector\": \"NETWORK\", \"attackComplexity\": \"HIGH\", \"privilegesRequired\": \"LOW\", \"userInteraction\": \"NONE\", \"scope\": \"UNCHANGED\", \"confidentialityImpact\": \"HIGH\", \"integrityImpact\": \"HIGH\", \"availabilityImpact\": \"NONE\"}, \"exploitabilityScore\": 1.6, \"impactScore\": 5.2}], \"cvssMetricV2\": [{\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"cvssData\": {\"version\": \"2.0\", \"vectorString\": \"AV:N/AC:M/Au:S/C:P/I:P/A:N\", \"baseScore\": 4.9, \"accessVector\": \"NETWORK\", \"accessComplexity\": \"MEDIUM\", \"authentication\": \"SINGLE\", \"confidentialityImpact\": \"PARTIAL\", \"integrityImpact\": \"PARTIAL\", \"availabilityImpact\": \"NONE\"}, \"baseSeverity\": \"MEDIUM\", \"exploitabilityScore\": 6.8, \"impactScore\": 4.9, \"acInsufInfo\": false, \"obtainAllPrivilege\": false, \"obtainUserPrivilege\": false, \"obtainOtherPrivilege\": false, \"userInteractionRequired\": false}]}",
      "published": "2021-03-05T18:15:13.067",
      "references": "[{\"url\": \"https://github.com/spiffe/spire/security/advisories/GHSA-q7gm-mjrg-44h9\", \"source\": \"cve@mitre.org\", \"tags\": [\"Patch\", \"Third Party Advisory\"]}, {\"url\": \"https://github.com/spiffe/spire/security/advisories/GHSA-q7gm-mjrg-44h9\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\", \"tags\": [\"Patch\", \"Third Party Advisory\"]}]",
      "sourceIdentifier": "cve@mitre.org",
      "vulnStatus": "Modified",
      "weaknesses": "[{\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"description\": [{\"lang\": \"en\", \"value\": \"CWE-863\"}]}]"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2021-27099\",\"sourceIdentifier\":\"cve@mitre.org\",\"published\":\"2021-03-05T18:15:13.067\",\"lastModified\":\"2024-11-21T05:57:20.980\",\"vulnStatus\":\"Modified\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"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\"},{\"lang\":\"es\",\"value\":\"En SPIRE versiones anteriores a 0.8.5, 0.9.4, 0.10.2, 0.11.3 y 0.12.1, el Node Attestor \\\"aws_iid\\\" normaliza inapropiadamente la ruta proporcionada por medio de la funcionalidad agent ID templating, lo que puede permitir la emisi\u00f3n de un ID de SPIFFE dentro del mismo dominio confiable, si el atacante controla el valor de una etiqueta EC2 antes de una certificaci\u00f3n, y el certificador est\u00e1 configurado para plantillas de ID de agente donde el valor de la etiqueta es el \u00faltimo elemento de la ruta.\u0026#xa0;Este problema ha sido corregido en versiones 0.11.3 y 0.12.1 de SPIRE\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N\",\"baseScore\":6.8,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"HIGH\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"NONE\"},\"exploitabilityScore\":1.6,\"impactScore\":5.2}],\"cvssMetricV2\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"2.0\",\"vectorString\":\"AV:N/AC:M/Au:S/C:P/I:P/A:N\",\"baseScore\":4.9,\"accessVector\":\"NETWORK\",\"accessComplexity\":\"MEDIUM\",\"authentication\":\"SINGLE\",\"confidentialityImpact\":\"PARTIAL\",\"integrityImpact\":\"PARTIAL\",\"availabilityImpact\":\"NONE\"},\"baseSeverity\":\"MEDIUM\",\"exploitabilityScore\":6.8,\"impactScore\":4.9,\"acInsufInfo\":false,\"obtainAllPrivilege\":false,\"obtainUserPrivilege\":false,\"obtainOtherPrivilege\":false,\"userInteractionRequired\":false}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-863\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:cncf:spire:*:*:*:*:*:*:*:*\",\"versionEndExcluding\":\"0.8.5\",\"matchCriteriaId\":\"0CFBEF70-490C-49D7-B601-CE2C8ED7AC99\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:cncf:spire:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"0.9.0\",\"versionEndExcluding\":\"0.9.4\",\"matchCriteriaId\":\"E7436751-C627-4143-A890-8B04D9C6642D\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:cncf:spire:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"0.10.0\",\"versionEndExcluding\":\"0.10.2\",\"matchCriteriaId\":\"E330A728-6B22-4C71-B37A-119BD2D3EADB\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:cncf:spire:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"0.11.0\",\"versionEndExcluding\":\"0.11.3\",\"matchCriteriaId\":\"EA57458D-53C5-4E8D-AFC2-D56826904304\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:cncf:spire:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"0.12.0\",\"versionEndExcluding\":\"0.12.1\",\"matchCriteriaId\":\"F05F1090-6FFC-4C74-B9D3-D63B3259A46A\"}]}]}],\"references\":[{\"url\":\"https://github.com/spiffe/spire/security/advisories/GHSA-q7gm-mjrg-44h9\",\"source\":\"cve@mitre.org\",\"tags\":[\"Patch\",\"Third Party Advisory\"]},{\"url\":\"https://github.com/spiffe/spire/security/advisories/GHSA-q7gm-mjrg-44h9\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Patch\",\"Third Party Advisory\"]}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.