Davidkorczynski

**Name of the Vulnerable Software and Affected Versions** Ruby JSON versions 2.14.0 through 2.15.2 Ruby JSON versions 2.17.1 through 2.17.1.2 Ruby JSON versions 2.19.0 through 2.19.2 **Description** Ruby JSON is a JSON implementation for Ruby. A format string injection issue exists when the `allow duplicate key: false` parsing option is used to parse user-supplied documents. This can lead to denial of service attacks or information disclosure. The `allow duplicate key: false` option is not enabled by default, so users who have not specifically enabled it are not affected. **Recommendations** Ruby JSON versions 2.14.0 through 2.15.2: Update to version 2.15.2.1 or later. Ruby JSON versions 2.17.1 through 2.17.1.2: Update to version 2.17.1.2 or later. Ruby JSON versions 2.19.0 through 2.19.2: Update to version 2.19.2 or later. Avoid using the `allow duplicate key: false` parsing option.

**Nome do software vulnerável e versões afetadas** Versões do Cosign anteriores à 2.2.4 **Descrição** O Cosign fornece assinatura de código e transparência para contêineres e binários. Artefatos de software criados com intenção maliciosa podem causar negação de serviço na máquina que executa o Cosign, afetando assim todos os serviços na máquina. A causa principal é que o Cosign cria fatias com base no número de assinaturas, manifestos ou atestados em artefatos não confiáveis. Assim, o artefato não confiável pode controlar a quantidade de memória que o Cosign aloca. O problema específico é que o Cosign aloca memória excessiva nas linhas que criam uma fatia com o mesmo comprimento dos manifestos. **Recomendações** Atualize para a versão 2.2.4 ou posterior, na qual o número de atestados, assinaturas e manifestos foi limitado a um valor razoável. Como solução alternativa temporária, considere restringir o uso de artefatos não confiáveis para minimizar o risco de exploração.

**Name of the Vulnerable Software and Affected Versions** Crossplane versions prior to 1.11.5 Crossplane versions prior to 1.12.3 Crossplane versions prior to 1.13.0 **Description** A high-privileged user could create a Package referencing an arbitrarily large image, which 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 create the Package and the eventually consistency nature of the controller. **Recommendations** For versions prior to 1.11.5, update to version 1.11.5 or later. For versions prior to 1.12.3, update to version 1.12.3 or later. For versions prior to 1.13.0, update to version 1.13.0 or later. As a temporary workaround, consider using images from trusted sources and keeping Package editing/creating privileges to administrators only.

**Name of the Vulnerable Software and Affected Versions** Crossplane versions prior to 1.11.5 Crossplane versions prior to 1.12.3 Crossplane versions prior to 1.13.0 **Description** Crossplane's image backend does not validate the byte contents of Crossplane packages, allowing an attacker to tamper with a package without detection. The issue has been fixed in versions 1.11.5, 1.12.3, and 1.13.0. As a workaround, users should only use images from trusted sources and keep package editing/creating privileges restricted to administrators. **Recommendations** For versions prior to 1.11.5, update to version 1.11.5 or later. For versions prior to 1.12.3, update to version 1.12.3 or later. For versions prior to 1.13.0, update to version 1.13.0 or later. As a temporary workaround, consider only using images from trusted sources and restricting package editing/creating privileges to administrators only.

**Name of the Vulnerable Software and Affected Versions** Rekor versions prior to 1.1.1 **Description** Rekor is an open source software supply chain transparency log that may crash due to out of memory (OOM) conditions caused by reading archive metadata files into memory without checking their sizes first. Verification of a JAR file submitted to Rekor can cause an out of memory crash if files within the META-INF directory of the JAR are sufficiently large. Parsing of an APK file submitted to Rekor can cause an out of memory crash if the .SIGN or .PKGINFO files within the APK are sufficiently large. **Recommendations** Update to Rekor version 1.1.1 to resolve the issue. As a temporary workaround, consider restricting the size of files within the META-INF directory of JAR files and the .SIGN and .PKGINFO files within APK files to prevent out of memory crashes. Avoid submitting JAR or APK files with large files in the META-INF directory or .SIGN and .PKGINFO files to Rekor until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** crossplane-runtime versions prior to 1.11.2 crossplane-runtime versions prior to 1.10.3 crossplane-runtime versions prior to 1.9.2 **Description** The issue affects crossplane-runtime, a set of Go libraries used to build Kubernetes controllers in Crossplane and its related stacks. An already highly privileged user able to create or update Compositions can specify an arbitrarily high index in a patch's `ToFieldPath`, which could lead to excessive memory usage once such Composition is selected for a Composite resource. Compositions allow users to specify patches inserting elements into arrays at an arbitrary index. When a Composition is selected for a Composite Resource, patches are evaluated and if a specified index is greater than the current size of the target slice, Crossplane will grow that slice up to the specified index, which could lead to an excessive amount of memory usage and therefore the Pod being OOM-Killed. **Recommendations** To resolve the issue for versions prior to 1.11.2, upgrade to version 1.11.2 or later. To resolve the issue for versions prior to 1.10.3, upgrade to version 1.10.3 or later. To resolve the issue for versions prior to 1.9.2, upgrade to version 1.9.2 or later. As a temporary workaround, restrict write privileges on Compositions to only admin users.

**Nome do software vulnerável e versões afetadas** Versões do Helm anteriores à 3.10.3 **Descrição** O problema diz respeito a uma referência a um ponteiro nulo no pacote ` repo ` do Helm, o que pode levar a uma negação de serviço. O pacote ` repo ` processa o arquivo de índice de um repositório e o carrega em estruturas com as quais o Go pode trabalhar. Certos arquivos de índice podem causar a criação de estruturas de dados em matriz, resultando em uma violação de memória. Quando tal arquivo de índice é encontrado, o cliente Helm entra em pânico, mas como o Helm não é um serviço de longa duração, esse pânico não afetará usos futuros do cliente Helm. Aplicativos que utilizam o pacote ` repo ` no SDK do Helm para analisar um arquivo de índice podem sofrer com esse problema quando a entrada causa um pânico do qual não é possível se recuperar. **Recomendações** Para versões anteriores à 3.10.3, atualize para a versão 3.10.3 para resolver o problema. Como solução alternativa temporária, os usuários do SDK podem validar se os arquivos de índice estão formatados corretamente antes de passá-los para as funções ` repo `.