CVSS: 9.8EPSS: 0%CPEs: 2EXPL: 1CVE-2023-38495 – Crossplane vulnerable to possible image tampering from missing image validation for Packages
https://notcve.org/view.php?id=CVE-2023-38495
Crossplane is a framework for building cloud native control planes without needing to write code. In versions prior to 1.11.5, 1.12.3, and 1.13.0, Crossplane's image backend does not validate the byte contents of Crossplane packages. As such, Crossplane does not detect if an attacker has tampered with a Package. The problem has been fixed in 1.11.5, 1.12.3 and 1.13.0. As a workaround, only use images from trusted sources and keep Package editing/creating privileges to administrators only. • https://github.com/crossplane/crossplane/blob/ac8b24fe739c5d942ea885157148497f196c3dd3/security/ADA-security-audit-23.pdf https://github.com/crossplane/crossplane/security/advisories/GHSA-pj4x-2xr5-w87m • CWE-20: Improper Input Validation •
CVSS: 3.4EPSS: 0%CPEs: 2EXPL: 1CVE-2023-37900 – Crossplane vulnerable to denial of service from large image
https://notcve.org/view.php?id=CVE-2023-37900
Crossplane is a framework for building cloud native control planes without needing to write code. In versions prior to 1.11.5, 1.12.3, and 1.13.0, a high-privileged user could create a Package referencing an arbitrarily large image containing that Crossplane would then parse, possibly resulting in exhausting all the available memory and therefore in the container being OOMKilled. The impact is limited due to the high privileges required to be able to create the Package and the eventually consistency nature of controller. This issue is fixed in versions 1.11.5, 1.12.3, and 1.13.0. • https://github.com/crossplane/crossplane/blob/ac8b24fe739c5d942ea885157148497f196c3dd3/security/ADA-security-audit-23.pdf https://github.com/crossplane/crossplane/security/advisories/GHSA-68p4-95xf-7gx8 • CWE-400: Uncontrolled Resource Consumption CWE-770: Allocation of Resources Without Limits or Throttling •
CVSS: 6.8EPSS: 0%CPEs: 5EXPL: 0CVE-2021-27099
https://notcve.org/view.php?id=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 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 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ón de un ID de SPIFFE dentro del mismo dominio confiable, si el atacante controla el valor de una etiqueta EC2 antes de una certificación, y el certificador está configurado para plantillas de ID de agente donde el valor de la etiqueta es el último elemento de la ruta. Este problema ha sido corregido en versiones 0.11.3 y 0.12.1 de SPIRE • https://github.com/spiffe/spire/security/advisories/GHSA-q7gm-mjrg-44h9 • CWE-863: Incorrect Authorization •
CVSS: 8.1EPSS: 0%CPEs: 5EXPL: 0CVE-2021-27098
https://notcve.org/view.php?id=CVE-2021-27098
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. 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ñadas para FetchX509SVID RPC de la API del Legacy Node de SPIRE Server, pueden resultar en una posible emisión de un Certificado X.509 con un URI SAN para un ID de SPIFFE que el agente no está autorizado a distribuir. Se presentan controles apropiados para requerir que la persona que llama presente un certificado de agente válido que ya esté 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. • https://github.com/spiffe/spire/security/advisories/GHSA-h746-rm5q-8mgq • CWE-295: Improper Certificate Validation •
CVSS: 7.3EPSS: 0%CPEs: 1EXPL: 0CVE-2020-8664 – envoy: Incorrect Access Control when using SDS with Combined Validation Context
https://notcve.org/view.php?id=CVE-2020-8664
CNCF Envoy through 1.13.0 has incorrect Access Control when using SDS with Combined Validation Context. Using the same secret (e.g. trusted CA) across many resources together with the combined validation context could lead to the “static” part of the validation context to be not applied, even though it was visible in the active config dump. CNCF Envoy versiones hasta 1.13.0, presenta un Control de Acceso incorrecto cuando se usa SDS con Contexto de Comprobación Combinada. Al utilizar el mismo secreto (por ejemplo, CA de confianza) a través de muchos recursos junto con el contexto de comprobación combinado podría conllevar a que la parte “static” del contexto de comprobación no sea aplicada, aún y cuando fuera visible en el volcado de la configuración activa. An access control bypass vulnerability was found in envoy. • https://access.redhat.com/errata/RHSA-2020:0734 https://github.com/envoyproxy/envoy/security/advisories/GHSA-3x9m-pgmg-xpx8 https://www.envoyproxy.io/docs/envoy/v1.13.1/intro/version_history https://access.redhat.com/security/cve/CVE-2020-8664 https://bugzilla.redhat.com/show_bug.cgi?id=1802542 • CWE-284: Improper Access Control CWE-287: Improper Authentication •