Nixpkgs Security Tracker

Login with GitHub

Suggestions search

With package: melange

Found 4 matching suggestions

updated 2 weeks, 2 days ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    6 packages
    • ocamlPackages.melange
    • ocamlPackages.melange-json
    • ocamlPackages_latest.melange
    • ocamlPackages.melange-json-native
    • ocamlPackages_latest.melange-json
    • ocamlPackages_latest.melange-json-native
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
melange affected by potential host command execution via license-check YAML mode patch pipeline

melange allows users to build apk packages using declarative pipelines. From version 0.10.0 to before 0.40.3, an attacker who can influence inputs to the patch pipeline could execute arbitrary shell commands on the build host. The patch pipeline in pkg/build/pipelines/patch.yaml embeds input-derived values (series paths, patch filenames, and numeric parameters) into shell scripts without proper quoting or validation, allowing shell metacharacters to break out of their intended context. The vulnerability affects the built-in patch pipeline which can be invoked through melange build and melange license-check operations. An attacker who can control patch-related inputs (e.g., through pull request-driven CI, build-as-a-service, or by influencing melange configurations) can inject shell metacharacters such as backticks, command substitutions $(…), semicolons, pipes, or redirections to execute arbitrary commands with the privileges of the melange build process. This issue has been patched in version 0.40.3.

Affected products

melange
  • ==>= 0.10.0, < 0.40.3

Matching in nixpkgs

Package maintainers

Upstream advisory: https://github.com/chainguard-dev/melange/security/advisories/GHSA-rf4g-89h5-crcr
Upstream patch: https://github.com/chainguard-dev/melange/commit/bd132535cd9f57d4bd39d9ead0633598941af030
updated 2 weeks, 2 days ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    6 packages
    • ocamlPackages.melange
    • ocamlPackages.melange-json
    • ocamlPackages_latest.melange
    • ocamlPackages.melange-json-native
    • ocamlPackages_latest.melange-json
    • ocamlPackages_latest.melange-json-native
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
melange pipeline working-directory could allow command injection

melange allows users to build apk packages using declarative pipelines. From version 0.3.0 to before 0.40.3, an attacker who can provide build input values, but not modify pipeline definitions, could execute arbitrary shell commands if the pipeline uses ${{vars.*}} or ${{inputs.*}} substitutions in working-directory. The field is embedded into shell scripts without proper quote escaping. This issue has been patched in version 0.40.3.

Affected products

melange
  • ==>= 0.3.0, < 0.40.3

Matching in nixpkgs

Package maintainers

Upstream advisory: https://github.com/chainguard-dev/melange/security/advisories/GHSA-vqqr-rmpc-hhg2
Upstream patch: https://github.com/chainguard-dev/melange/commit/e51ca30cfb63178f5a86997d23d3fff0359fa6c8
updated 2 weeks, 2 days ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    6 packages
    • ocamlPackages.melange
    • ocamlPackages.melange-json
    • ocamlPackages_latest.melange
    • ocamlPackages.melange-json-native
    • ocamlPackages_latest.melange-json
    • ocamlPackages_latest.melange-json-native
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
melange has a path traversal in license-path which allows reading files outside workspace

melange allows users to build apk packages using declarative pipelines. From version 0.14.0 to before 0.40.3, an attacker who can influence a melange configuration file (e.g., through pull request-driven CI or build-as-a-service scenarios) could read arbitrary files from the host system. The LicensingInfos function in pkg/config/config.go reads license files specified in copyright[].license-path without validating that paths remain within the workspace directory, allowing path traversal via ../ sequences. The contents of the traversed file are embedded into the generated SBOM as license text, enabling exfiltration of sensitive data through build artifacts. This issue has been patched in version 0.40.3.

Affected products

melange
  • ==>= 0.14.0, < 0.40.3

Matching in nixpkgs

Package maintainers

Upstream advisory: https://github.com/chainguard-dev/melange/security/advisories/GHSA-2w4f-9fgg-q2v9
Upstream patch: https://github.com/chainguard-dev/melange/commit/2f95c9f4355ed993f2670bf1bb82d88b0f65e9e4
updated 2 weeks, 2 days ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    6 packages
    • ocamlPackages.melange
    • ocamlPackages.melange-json
    • ocamlPackages.melange-json-native
    • ocamlPackages_latest.melange
    • ocamlPackages_latest.melange-json
    • ocamlPackages_latest.melange-json-native
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
melange QEMU runner could write files outside workspace directory

melange allows users to build apk packages using declarative pipelines. In version 0.11.3 to before 0.40.3, an attacker who can influence the tar stream from a QEMU guest VM could write files outside the intended workspace directory on the host. The retrieveWorkspace function extracts tar entries without validating that paths stay within the workspace, allowing path traversal via ../ sequences. This issue has been patched in version 0.40.3.

Affected products

melange
  • ==>= 0.11.3, < 0.40.3

Matching in nixpkgs

Package maintainers

Upstream advisory: https://github.com/chainguard-dev/melange/security/advisories/GHSA-qxx2-7h4c-83f4
Upstream patch: https://github.com/chainguard-dev/melange/commit/6e243d0d46699f837d7c392397a694d2bcc7612b