Bug 58602 - wpa: Multiple issues (5.2)
Summary: wpa: Multiple issues (5.2)
Status: CLOSED FIXED
Alias: None
Product: UCS
Classification: Unclassified
Component: Security updates
Version: UCS 5.2
Hardware: All Linux
: P3 normal
Target Milestone: UCS 5.2-3-errata
Assignee: Quality Assurance
QA Contact: Dirk Wiesenthal
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-09-10 10:52 CEST by Quality Assurance
Modified: 2025-09-17 14:08 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Security Issue
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Customer ID:
Max CVSS v3 score: 6.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N) NVD


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Quality Assurance univentionstaff 2025-09-10 10:52:35 CEST
New Debian wpa 2:2.10-12+deb12u3A~5.2.3.202509101046 fixes:
This update addresses the following issue:
2:2.10-12+deb12u3 (Fri, 11 Apr 2025 16:29:46 +0200)
* Non-maintainer upload by the LTS Security Team.
* debian/patches/CVE-2022-37660.patch: Add hostapd_dpp_pkex_clear_code() and  wpas_dpp_pkex_clear_code(), and clear code reusage in  ./src/ap/dpp_hostapd.c and ./wpa_supplicant/dpp_supplicant.c
* Fix CVE-2022-37660: the PKEX code remains active even after a successful  PKEX association. An attacker that successfully bootstrapped public keys  with another entity using PKEX in the past, will be able to subvert a  future bootstrapping by passively observing public keys, re-using the  encrypting element Qi and subtracting it from the captured message M (X = M  - Qi). This will result in the public ephemeral key X; the only element  required to subvert the PKEX association
Comment 1 Quality Assurance univentionstaff 2025-09-10 12:00:22 CEST
--- mirror/ftp/pool/main/w/wpa/wpa_2.10-12+deb12u2A~5.2.0.202409021018.dsc
+++ apt/ucs_5.2-0-errata5.2-3/source/wpa_2.10-12+deb12u3A~5.2.3.202509101046.dsc
@@ -1,10 +1,25 @@
-2:2.10-12+deb12u2A~5.2.0.202409021018 [Mon, 02 Sep 2024 10:34:30 -0000] Univention builddaemon <buildd@univention.de>:
+2:2.10-12+deb12u3A~5.2.3.202509101046 [Wed, 10 Sep 2025 10:52:45 -0000] Univention builddaemon <buildd@univention.de>:
 
   * UCS auto build. The following patches have been applied to the original source package
     eapol_test.patch
     eapol_test.quilt
     examples.patch
 
+2:2.10-12+deb12u3 [Fri, 11 Apr 2025 16:29:46 +0200] Bastien Roucariès <rouca@debian.org>:
+
+  * Non-maintainer upload by the LTS Security Team.
+  * debian/patches/CVE-2022-37660.patch: Add hostapd_dpp_pkex_clear_code()
+    and wpas_dpp_pkex_clear_code(), and clear code reusage in
+    ./src/ap/dpp_hostapd.c and ./wpa_supplicant/dpp_supplicant.c
+  * Fix CVE-2022-37660: the PKEX code remains active even after
+    a successful PKEX association. An attacker that successfully
+    bootstrapped public keys with another entity using PKEX in
+    the past, will be able to subvert a future bootstrapping by
+    passively observing public keys, re-using the encrypting
+    element Qi and subtracting it from the captured message
+    M (X = M - Qi). This will result in the public ephemeral
+    key X; the only element required to subvert the PKEX association
+
 2:2.10-12+deb12u2 [Mon, 05 Aug 2024 21:07:00 +0200] Salvatore Bonaccorso <carnil@debian.org>:
 
   * Non-maintainer upload by the Security Team.

<http://piuparts.knut.univention.de/5.2-3/#1305046114551200737>
Comment 2 Dirk Wiesenthal univentionstaff 2025-09-11 17:54:53 CEST
OK: YAML
OK: Tests
OK: piuparts
Comment 3 Christian Castens univentionstaff 2025-09-17 14:08:57 CEST
<https://errata.software-univention.de/#/?erratum=5.2x216>