!ZRgXNaHrdpGqwUnGnj:nixos.org

NixOS Security Triage

687 Members
Coordination and triage of security issues in nixpkgs215 Servers

Load older messages


SenderMessageTime
2 Jul 2024
@ity:itycodes.org@ity:itycodes.org changed their display name from Tranquil Ity to Tranquil Ity (eepy/cutie).20:49:29
@ity:itycodes.org@ity:itycodes.org changed their display name from Tranquil Ity (eepy/cutie) to Tranquil Ity.20:50:51
@r_i_s:matrix.orgris_sigh https://codeanlabs.com/blog/research/cve-2024-29510-ghostscript-format-string-exploitation/21:26:14
@tgerbet:matrix.orgtgerbethttps://github.com/NixOS/nixpkgs/commit/2dcfa4787b6fb9fb9e6cb087db382f9ce8556f9921:32:15
@emilazy:matrix.orgemily(don't expose unsandboxed ghostscript to untrusted input folks)21:34:09
@r_i_s:matrix.orgris_
In reply to @tgerbet:matrix.org
https://github.com/NixOS/nixpkgs/commit/2dcfa4787b6fb9fb9e6cb087db382f9ce8556f99
oh awesome we don't even have to backport
21:41:00
@hexa:lossy.networkhexahttps://httpd.apache.org/security/vulnerabilities_24.html22:08:47
3 Jul 2024
@janik0:matrix.org@janik0:matrix.org left the room.07:23:26
@hexa:lossy.networkhexahttps://mastodon.social/@MastodonEngineering/112717731749830186 mastodon, 2024-07-04 16:00 UTC13:16:04
@tgerbet:matrix.orgtgerbet* 15:00 UTC13:21:50
@hexa:lossy.networkhexahttps://github.com/NixOS/nixpkgs/pull/324349 https://meta.discourse.org/t/3-2-3-security-and-bug-fix-release/31339215:22:47
@hexa:lossy.networkhexahttps://github.com/NixOS/nixpkgs/pull/32437116:04:16
@lassulus:lassul.uslassulus joined the room.19:11:43
@shaderoit99:matrix.org@shaderoit99:matrix.org left the room.21:28:15
4 Jul 2024
@eyjhb:eyjhb.dk@eyjhb:eyjhb.dk left the room.10:58:00
@os:matrix.flyingcircus.ioosnyx (he/him)https://github.com/mastodon/mastodon/releases/tag/v4.2.1015:05:18
@hexa:lossy.networkhexamaintainer is working on it15:09:02
@hexa:lossy.networkhexa(kerstin)15:09:03
@hexa:lossy.networkhexahttps://github.com/NixOS/nixpkgs/pull/324586 merged into master, unstable-small eval trigggered15:39:17
@hexa:lossy.networkhexahttps://github.com/NixOS/nixpkgs/pull/324587 still running tests15:39:23
@philiptaron:matrix.orgPhilip Taron (UTC-8) left the room.15:45:55
@philiptaron:matrix.orgPhilip Taron (UTC-8) joined the room.15:55:52
@hexa:lossy.networkhexa * https://github.com/NixOS/nixpkgs/pull/324587 merged into release-24.05, nixos-24.05-small eval triggered15:59:31
@erictapen:chat.ccc-p.orgKerstin (she/her) joined the room.16:01:33
@soispha:vhack.euBenedikt changed their display name from Soispha to Benedikt.19:10:30
5 Jul 2024
@septem9er:fairydust.spaceSeptem9er

Hey,
it seems like there is an regression of CVE-2023-36476 in the Nixos-calamares-extension, aka. the graphical NixOS-Installer.
The commit fixing this was reverted for some reason. It seems like they wanted to fix it another way in this commit. I haven't really looked into what they try to do in this commit, however the commit message was the following:

Do not use crypto_keyfile.bin in UEFI, but leave BIOS the same.

Which doesn't really make sense to me, because the original CVE applied to BIOS systems mostly. So leaving BIOS systems the same wouldn't fix the issue.

Someone reported this here, I could reproduce this with the latest Nixos-GNOME ISO, with the following steps:

  1. Start the ISO on a BIOS (legacy) system / in BIOS mode
  2. Select manual partitioning in the installer
  3. Create an unencrypted legacy-boot partition with mountpoint /boot
  4. Create an encrypted root partition with mountpoint /

After the installation is done, there is an luks-keyfile in an zstd/cpio archive in /boot/kernels/***-secrets, which does open the root partition.

11:36:34
@emilazy:matrix.orgemilythank you for the report11:48:34
@emilazy:matrix.orgemilyhttps://github.com/NixOS/calamares-nixos-extensions/pull/25 says "#21 broke encrypted swap by mishandling the removal of crypto_keyfile.bin. This reverts the original fix. Instead, we leave BIOS the same; that was secure as it was before", I guess this was just a misunderstanding of the vuln? :/11:49:21
@emilazy:matrix.orgemilymaybe it's better to revert and let encrypted swap be broken while we figure out what the proper fix is?11:50:59
@emilazy:matrix.orgemily(I guess this is going to require another GHSA? it's the month of security regressions…)11:51:25

Show newer messages


Back to Room ListRoom Version: 6