FKIE_CVE-2021-27098

Vulnerability from fkie_nvd - Published: 2021-03-05 17:15 - Updated: 2024-11-21 05:57
Severity ?
8.1 (High) - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
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.
References
cve@mitre.orghttps://github.com/spiffe/spire/security/advisories/GHSA-h746-rm5q-8mgqThird Party Advisory
af854a3a-2127-422b-91ae-364da2661108https://github.com/spiffe/spire/security/advisories/GHSA-h746-rm5q-8mgqThird Party Advisory
Impacted products
Vendor Product Version
cncf spire *
cncf spire *
cncf spire *
cncf spire *
cncf spire *
To clipboard 

{
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:cncf:spire:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "53FC0C26-EC3F-45EE-ADAC-FC283813FBE1",
              "versionEndIncluding": "0.8.4",
              "versionStartIncluding": "0.8.1",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:a:cncf:spire:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "E7436751-C627-4143-A890-8B04D9C6642D",
              "versionEndExcluding": "0.9.4",
              "versionStartIncluding": "0.9.0",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:a:cncf:spire:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "E330A728-6B22-4C71-B37A-119BD2D3EADB",
              "versionEndExcluding": "0.10.2",
              "versionStartIncluding": "0.10.0",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:a:cncf:spire:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "EA57458D-53C5-4E8D-AFC2-D56826904304",
              "versionEndExcluding": "0.11.3",
              "versionStartIncluding": "0.11.0",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:a:cncf:spire:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "F05F1090-6FFC-4C74-B9D3-D63B3259A46A",
              "versionEndExcluding": "0.12.1",
              "versionStartIncluding": "0.12.0",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "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\u2019s 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."
    },
    {
      "lang": "es",
      "value": "En SPIRE versiones 0.8.1 hasta 0.8.4 y versiones anteriores a 0.9.4, 0.10.2, 0.11.3 y 0.12.1, unas peticiones especialmente dise\u00f1adas para FetchX509SVID RPC de la API del Legacy Node de SPIRE Server, pueden resultar en una posible emisi\u00f3n de un Certificado X.509 con un URI SAN para un ID de SPIFFE que el agente no est\u00e1 autorizado a distribuir.\u0026#xa0;Se presentan controles apropiados para requerir que la persona que llama presente un certificado de agente v\u00e1lido que ya est\u00e9 autorizado para emitir al menos un ID de SPIFFE, y que el ID de SPIFFE pedido pertenezca al mismo dominio confiable, antes de poder desencadenar esta vulnerabilidad.\u0026#xa0;Este problema ha sido corregido en versiones 0.8.5, 0.9.4, 0.10.2, 0.11.3 y 0.12.1 de SPIRE"
    }
  ],
  "id": "CVE-2021-27098",
  "lastModified": "2024-11-21T05:57:20.830",
  "metrics": {
    "cvssMetricV2": [
      {
        "acInsufInfo": false,
        "baseSeverity": "MEDIUM",
        "cvssData": {
          "accessComplexity": "LOW",
          "accessVector": "NETWORK",
          "authentication": "SINGLE",
          "availabilityImpact": "NONE",
          "baseScore": 5.5,
          "confidentialityImpact": "PARTIAL",
          "integrityImpact": "PARTIAL",
          "vectorString": "AV:N/AC:L/Au:S/C:P/I:P/A:N",
          "version": "2.0"
        },
        "exploitabilityScore": 8.0,
        "impactScore": 4.9,
        "obtainAllPrivilege": false,
        "obtainOtherPrivilege": false,
        "obtainUserPrivilege": false,
        "source": "nvd@nist.gov",
        "type": "Primary",
        "userInteractionRequired": false
      }
    ],
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 8.1,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "LOW",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 2.8,
        "impactScore": 5.2,
        "source": "nvd@nist.gov",
        "type": "Primary"
      }
    ]
  },
  "published": "2021-03-05T17:15:14.920",
  "references": [
    {
      "source": "cve@mitre.org",
      "tags": [
        "Third Party Advisory"
      ],
      "url": "https://github.com/spiffe/spire/security/advisories/GHSA-h746-rm5q-8mgq"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "tags": [
        "Third Party Advisory"
      ],
      "url": "https://github.com/spiffe/spire/security/advisories/GHSA-h746-rm5q-8mgq"
    }
  ],
  "sourceIdentifier": "cve@mitre.org",
  "vulnStatus": "Modified",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-295"
        }
      ],
      "source": "nvd@nist.gov",
      "type": "Primary"
    }
  ]
}


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.