NixOS Security Triage | 699 Members | |
| Coordination and triage of security issues in nixpkgs | 216 Servers |
| Sender | Message | Time |
|---|---|---|
| 8 Apr 2024 | ||
| * Cherrypick/patch or wait? I'd wait. | 15:18:28 | |
| Another reminder to drop support for 1.1.1, when possible :) | 15:19:00 | |
| Envoy 1.27.4 (CVE-2024-30255) https://github.com/envoyproxy/envoy/releases/tag/v1.27.4 cc lukegb (he/him) (build is already kind of broken and only work thanks to caching of the deps :/ ) | 18:21:01 | |
| 23:11:17 | ||
| 9 Apr 2024 | ||
| The security researchers at exploit.org claimed they've found an RCE in Telegram Desktop's latest version (seems 4.16.1 at least), and updated a demonstration video targeting Windows build. Someone in the comment claimed they could not trigger the PoC in 4.16.4. Original message:
| 06:00:20 | |
| * The security researchers at exploit.org claimed they've found an RCE in Telegram Desktop's latest version (seems 4.16.1 at least), and updated a demonstration video targeting Windows build. Someone in the comment claimed they could not trigger the PoC in 4.16.4. Original message:
Link: https://t.me/exploitorg/30 | 06:00:32 | |
| * The security researchers at exploit.org claimed they've found an RCE in Telegram Desktop's latest version (seems 4.16.1 at least), and updated a demonstration video targeting Windows build. Someone in the comment claimed they could not trigger the PoC in 4.16.4. Currently 23.11 and unstable branch has 4.16.1, and master was updated to 4.16.4 yesterday. Original message:
Link: https://t.me/exploitorg/30 | 06:01:09 | |
| 12:26:57 | ||
| * The security researchers at exploit.org claimed they've found an RCE in Telegram Desktop's latest version (seems 4.16.1 at least), and updated a demonstration video targeting Windows build. Someone in the comment claimed they could not trigger the PoC in 4.16.4. Currently 23.11 and unstable branch has 4.16.1, and master was updated to 4.16.4 yesterday. Original message: Link: https://t.me/exploitorg/30 Edit: telegram official said they could not find the vulnerability and the demonstration video is likely staged. https://twitter.com/telegram/status/1777677055837995151 | 12:50:10 | |
| 13:24:35 | ||
| 23:12:29 | ||
| 23:22:53 | ||
| Alas, I am travelling and don't really have time rn | 23:49:14 | |
| 10 Apr 2024 | ||
| Redacted or Malformed Event | 04:55:35 | |
| 05:15:59 | ||
| 20:29:23 | ||
| https://github.com/YuriiCrimson/ExploitGSM/ anyone aware of this security vulnerability? | 20:29:46 | |
| That repo looks extremely sus and the behavior of the author is also very weird | 20:33:21 | |
| * That repo looks extremely sus and the behavior of the author is also very weird, lets follow up in #security-discuss:nixos.org if need be | 20:33:52 | |
| Alright | 20:34:11 | |
| 11 Apr 2024 | ||
| 20:44:07 | ||
| 12 Apr 2024 | ||
| 08:07:21 | ||
| * The security researchers at exploit.org claimed they've found an RCE in Telegram Desktop's latest version (seems 4.16.1 at least), and updated a demonstration video targeting Windows build. Someone in the comment claimed they could not trigger the PoC in 4.16.4. Currently 23.11 and unstable branch has 4.16.1, and master was updated to 4.16.4 yesterday. Original message: Link: https://t.me/exploitorg/30 Edit: telegram official said they could not find the vulnerability and the demonstration video is likely staged. https://twitter.com/telegram/status/1777677055837995151 Edit again: RCE confirmed but not zero-click. The user have to click a file that appear to be video files. Affected versions are 4.16.0 to 4.16.6. | 11:24:06 | |
| https://www.openwall.com/lists/oss-security/2024/04/12/11 | 20:46:12 | |
| * https://www.openwall.com/lists/oss-security/2024/04/12/11 php | 20:46:32 | |
| ma27 | 20:48:00 | |
| huh, nobody was faster? fine, on it. | 20:48:50 | |
| https://github.com/NixOS/nixpkgs/pull/303711 | 21:05:00 | |
| 13 Apr 2024 | ||
| 08:27:37 | ||
| https://chromereleases.googleblog.com/2024/04/stable-channel-update-for-desktop_10.html cc emily | 11:06:14 | |