CVE-2023-32189 json
Insecure handling SSH key in SUSE Manager when bootstrapping new clients
published 2024-10-16 2 y ago modified 2026-06-17 4 mo ago also EUVD-2023-36454
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 3%
- public exploits
- 0
- none known
Summary
Insecure handling of ssh keys used to bootstrap clients allows local attackers to potentially gain access to the keys
Patch / fix
- SUSE SUSE Manager Server Module 4.3 4.3.27-150400.3.38.2
- release-notes-susemanager Manager Server 4.3 4.3.11-150400.3.100.1
- release-notes-susemanager-proxy Manager Proxy 4.3 4.3.11-150400.3.79.1
- jose4j Manager Server Module 4.3 0.5.1-150400.3.6.2
- cobbler Manager Server Module 4.3 3.3.3-150400.5.39.5
- spacecmd Manager Server Module 4.3, Manager Proxy Module 4.3 4.3.26-150400.3.33.5
- mgr-daemon Manager Proxy Module 4.3 4.3.8-150400.3.12.5
- susemanager Manager Server Module 4.3 4.3.34-150400.3.45.5
- spacewalk-web Manager Server Module 4.3, Manager Proxy Module 4.3 4.3.37-150400.3.39.7
suse advisories SUSE-SU-2024:0513-1SUSE-SU-2024:0485-1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.15% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N |
| CNA | 4.0 | 6.4 | CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:H/SA:H |
| CNA | 4.0 | 6.4 | CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- SUSE SUSE Manager Server Module 4.3
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
References
Sources
- CVE List CVE-2023-32189
- NVD CVE-2023-32189
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.