CVE-2024-47174

{"id": "CVE-2024-47174", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.9, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 3.6, "exploitabilityScore": 2.2}]}, "published": "2024-09-26T18:15:10.840", "references": [{"url": "https://github.com/NixOS/nix/commit/062b4a489e30da9c85fa4ff15cfdd2e51cac7b90", "source": "security-advisories@github.com"}, {"url": "https://github.com/NixOS/nix/commit/5db358d4d78aea7204a8f22c5bf2a309267ee038", "source": "security-advisories@github.com"}, {"url": "https://github.com/NixOS/nix/pull/11585", "source": "security-advisories@github.com"}, {"url": "https://github.com/NixOS/nix/security/advisories/GHSA-6fjr-mq49-mm2c", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-287"}]}], "descriptions": [{"lang": "en", "value": "Nix is a package manager for Linux and other Unix systems. Starting in version 1.11 and prior to versions 2.18.8 and 2.24.8, `<nix/fetchurl.nix>` did not verify TLS certificates on HTTPS connections. This could lead to connection details such as full URLs or credentials leaking in case of a man-in-the-middle (MITM) attack. `<nix/fetchurl.nix>` is also known as the builtin derivation builder `builtin:fetchurl`. It's not to be confused with the evaluation-time function `builtins.fetchurl`, which was not affected by this issue. A user may be affected by the risk of leaking credentials if they have a `netrc` file for authentication, or rely on derivations with `impureEnvVars` set to use credentials from the environment. In addition, the commonplace trust-on-first-use (TOFU) technique of updating dependencies by specifying an invalid hash and obtaining it from a remote store was also vulnerable to a MITM injecting arbitrary store objects. This also applied to the impure derivations experimental feature. Note that this may also happen when using Nixpkgs fetchers to obtain new hashes when not using the fake hash method, although that mechanism is not implemented in Nix itself but rather in Nixpkgs using a fixed-output derivation. The behavior was introduced in version 1.11 to make it consistent with the Nixpkgs `pkgs.fetchurl` and to make `<nix/fetchurl.nix>` work in the derivation builder sandbox, which back then did not have access to the CA bundles by default. Nowadays, CA bundles are bind-mounted on Linux. This issue has been fixed in Nix 2.18.8 and 2.24.8. As a workaround, implement (authenticated) fetching with `pkgs.fetchurl` from Nixpkgs, using `impureEnvVars` and `curlOpts` as needed."}, {"lang": "es", "value": "Nix es un administrador de paquetes para Linux y otros sistemas Unix. A partir de la versi\u00f3n 1.11 y antes de las versiones 2.18.8 y 2.24.8, `` no verificaba los certificados TLS en las conexiones HTTPS. Esto podr\u00eda provocar que se filtraran detalles de la conexi\u00f3n, como URL completas o credenciales, en caso de un ataque de intermediario (MITM). `` tambi\u00e9n se conoce como el generador de derivaciones integrado `builtin:fetchurl`. No debe confundirse con la funci\u00f3n de tiempo de evaluaci\u00f3n `builtins.fetchurl`, que no se vio afectada por este problema. Un usuario puede verse afectado por el riesgo de filtrar credenciales si tiene un archivo `netrc` para la autenticaci\u00f3n o conf\u00eda en derivaciones con `impureEnvVars` configuradas para usar credenciales del entorno. Adem\u00e1s, la t\u00e9cnica com\u00fan de confianza en el primer uso (TOFU) de actualizar dependencias especificando un hash no v\u00e1lido y obteni\u00e9ndolo de un almac\u00e9n remoto tambi\u00e9n era vulnerable a un MITM que inyectara objetos de almac\u00e9n arbitrarios. Esto tambi\u00e9n se aplicaba a la caracter\u00edstica experimental de derivaciones impuras. Tenga en cuenta que esto tambi\u00e9n puede suceder cuando se utilizan los recuperadores de Nixpkgs para obtener nuevos hashes cuando no se utiliza el m\u00e9todo de hash falso, aunque ese mecanismo no est\u00e1 implementado en Nix en s\u00ed, sino en Nixpkgs que utiliza una derivaci\u00f3n de salida fija. El comportamiento se introdujo en la versi\u00f3n 1.11 para que fuera coherente con el `pkgs.fetchurl` de Nixpkgs y para que `` funcionara en el entorno limitado del generador de derivaciones, que en ese entonces no ten\u00eda acceso a los paquetes de CA de forma predeterminada. Hoy en d\u00eda, los paquetes de CA se montan mediante enlaces en Linux. Este problema se ha solucionado en Nix 2.18.8 y 2.24.8. Como workaround, implemente la obtenci\u00f3n (autenticada) con `pkgs.fetchurl` desde Nixpkgs, usando `impureEnvVars` y `curlOpts` seg\u00fan sea necesario."}], "lastModified": "2024-09-30T12:46:20.237", "sourceIdentifier": "security-advisories@github.com"}