!ZRgXNaHrdpGqwUnGnj:nixos.org

NixOS Security Triage

713 Members
Coordination and triage of security issues in nixpkgs219 Servers

Load older messages


SenderMessageTime
6 Nov 2023
@k900:0upti.meK900Honestly I think it's fine to delay until the next cycle16:05:56
@vcunat:matrix.orgvcunatIf it's merged with a stdenv rebuild and you care enough to patch 🤷16:12:42
@hexa:lossy.networkhexa
OpenSSL Security Advisory [6th November 2023]
=============================================

Excessive time spent in DH check / generation with large Q parameter value (CVE-2023-5678)
==========================================================================================

Severity: Low

Issue summary: Generating excessively long X9.42 DH keys or checking
excessively long X9.42 DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_generate_key() to
generate an X9.42 DH key may experience long delays.  Likewise, applications
that use DH_check_pub_key(), DH_check_pub_key_ex() or EVP_PKEY_public_check()
to check an X9.42 DH key or X9.42 DH parameters may experience long delays.
Where the key or parameters that are being checked have been obtained from
an untrusted source this may lead to a Denial of Service.

While DH_check() performs all the necessary checks (as of CVE-2023-3817),
DH_check_pub_key() doesn't make any of these checks, and is therefore
vulnerable for excessively large P and Q parameters.

Likewise, while DH_generate_key() performs a check for an excessively large
P, it doesn't check for an excessively large Q.

An application that calls DH_generate_key() or DH_check_pub_key() and
supplies a key or parameters obtained from an untrusted source could be
vulnerable to a Denial of Service attack.

DH_generate_key() and DH_check_pub_key() are also called by a number of
other OpenSSL functions.  An application calling any of those other
functions may similarly be affected.  The other functions affected by this
are DH_check_pub_key_ex(), EVP_PKEY_public_check(), and EVP_PKEY_generate().

Also vulnerable are the OpenSSL pkey command line application when using the
"-pubcheck" option, as well as the OpenSSL genpkey command line application.

The OpenSSL SSL/TLS implementation is not affected by this issue.

The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.

OpenSSL 3.1, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.

Due to the low severity of this issue we are not issuing new releases of
OpenSSL at this time. The fix will be included in the next releases when they
become available.
The fix is also available in commit ddeb4b6c6d527e54ce9a99cba785c0f7776e54b6
(for 3.1) and commit db925ae2e65d0d925adef429afc37f75bd1c2017 (for 3.0).
It is available to premium support customers in commit
710fee740904b6290fef0dd5536fbcedbc38ff0c (for 1.1.1) and in commit
34efaef6c103d636ab507a0cc34dca4d3aecc055 (for 1.0.2). 

This issue was reported on 16th August 2023 by David Benjamin (Google). The
fix was developed by Richard Levitte.
16:14:40
@makefu:fairydust.spacemakefu left the room.18:47:43
7 Nov 2023
@abbe:badti.me@abbe:badti.me changed their profile picture.20:13:07
8 Nov 2023
@hexa:lossy.networkhexahttps://www.openwall.com/lists/oss-security/2023/11/08/719:09:56
@hexa:lossy.networkhexarelease-23.05 on 12.0.0 and 13.0.0 on master19:10:50
@hexa:lossy.networkhexahttps://github.com/NixOS/nixpkgs/issues/26632019:23:48
9 Nov 2023
@dgrig:erethon.comdgrig joined the room.15:36:58
10 Nov 2023
@atka:matrix.org@atka:matrix.org left the room.07:35:29
11 Nov 2023
@ninjatrappeur:alternativebit.fr@ninjatrappeur:alternativebit.fr left the room.07:14:53
12 Nov 2023
@toonn:matrix.orgtoonn changed their profile picture.17:53:51
@hexa:lossy.networkhexa apache-airflow https://www.openwall.com/lists/oss-security/2023/11/12/1 https://www.openwall.com/lists/oss-security/2023/11/12/2 18:41:26
14 Nov 2023
@julian:nekover.se@julian:nekover.se changed their display name from Julian to June.02:20:57
@hexa:lossy.networkhexa https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20231114 16:43:25
@vyls:matrix.org@vyls:matrix.org left the room.18:21:42
@void68:matrix.orgvoid
In reply to @hexa:lossy.network
https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20231114

Name of the issue: Redundant Prefix Issue

Description of the issue
Under certain microarchitectural conditions, Intel has identified cases
where execution of an instruction (REP MOVSB) encoded with a redundant
REX prefix may result in unpredictable system behavior resulting in a
system crash/hang, or, in some limited scenarios, may allow escalation
of privilege from CPL3 to CPL0.
This Redundant Prefix Issue is assigned CVE-2023-23583 with a CVSS Base
Score of 8.8 High CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.

19:29:02
@zzywysm:matrix.orgzzywysmhttps://www.bleepingcomputer.com/news/security/new-cachewarp-amd-cpu-attack-lets-hackers-gain-root-in-linux-vms/20:56:02
@k900:0upti.meK900Awful headline20:57:40
@k900:0upti.meK900CacheWarp affects only AMD systems with the following processors that come with SEV support: 1st Gen AMD EPYC Processors (SEV and SEV-ES) 2nd Gen AMD EPYC Processors (SEV and SEV-ES) 3rd Gen AMD EPYC Processors (SEV, SEV-ES, SEV-SNP) According to AMD's advisory, the issue does not impact AMD 4th generation 'Genoa' EPYC processors (Zen 4 microarchitecture). The company says there is no mitigation for first or second generations of EPYC processors because the SEV and SEV-ES features lack protection functionality for guest VM memory, while the SEV-SNP feature is unavailable.20:58:04
@k900:0upti.meK900Also20:58:49
@k900:0upti.meK900Improper or unexpected behavior of the INVD instruction in some AMD CPUs may allow an attacker with a malicious hypervisor to affect cache line write-back behavior of the CPU leading to a potential loss of guest virtual machine (VM) memory integrity.20:58:51
@k900:0upti.meK900So basically this is only relevant for systems running trusted VMs on an untrusted hypervisor20:59:16
@k900:0upti.meK900 Which is exceptionally rare 20:59:20
15 Nov 2023
@kranzes:matrix.orgkranzes joined the room.12:38:37
@grahamc:nixos.org@grahamc:nixos.orgchanged room power levels.16:15:29
@grahamc:nixos.org@grahamc:nixos.org left the room.16:15:30
@qyliss:fairydust.spaceAlyssa Ross 17:09:01
@mjolnir:nixos.orgNixOS Moderation Botchanged room power levels.18:12:06
@eisfunke:eisfunke.com@eisfunke:eisfunke.com changed their profile picture.22:42:12

Show newer messages


Back to Room ListRoom Version: 6