treewide: add CVE-2024-9680 as a known vulnerability to Firefox forks

[Scrumplex]

See https://www.mozilla.org/en-US/security/advisories/mfsa2024-51/#CVE-2024-9680

Floorp: Floorp-Projects/Floorp#1468
Librewolf: Waiting for AppImage update

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[emilazy]

I am not sure we should be carrying Firefox forks that need us to notify them of critical RCE CVEs. If Floorp don’t react quickly we might want to consider removal.

[github-actions]

Backport failed for release-24.05, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release-24.05
git worktree add -d .worktree/backport-347601-to-release-24.05 origin/release-24.05
cd .worktree/backport-347601-to-release-24.05
git switch --create backport-347601-to-release-24.05
git cherry-pick -x b119e084e6d09367fe4fe84f4f384be90cbb6421 73223431f76e311407b0e5ede9e8fceb11dc5e50

[SuperSandro2000]

I am asking again why knowVulnerabilities prevents Hydra builds. It makes no sense and forbids anyone without a compile server to still use the package. It is more or less equal to marking the package broken.

[emilazy]

For some packages I can understand it, but… why on earth would you want to use a Firefox variant with a remote code execution vulnerability being actively exploited in the wild?