Security Resilience

CVE-2023-32188

Published
16 October 2024
Modified
15 April 2026
CVSS Score v4 9.4
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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
EPSS Score 0.0059 47th percentile
Risk Priority 41 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-32188 is a critical-severity Generation of Incorrect Security Tokens (CWE-1270) vulnerability in Suse (inferred from references). Its CVSS base score is 9.4 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Protocol or Service Impersonation (T1001.003); ranked at the 47th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and AC-16 (Security and Privacy Attributes) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

A user can reverse engineer the JWT token (JSON Web Token) used in authentication for Manager and API access, forging a valid NeuVector Token to perform malicious activity in NeuVector. This can lead to an RCE.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.003 Protocol or Service Impersonation Command And Control
Adversaries may impersonate legitimate protocols or web service traffic to disguise command and control activity and thwart analysis efforts.
T1003.002 Security Account Manager Credential Access
Adversaries may attempt to extract credential material from the Security Account Manager (SAM) database either through in-memory techniques or through the Windows Registry where the SAM database is stored.
T1003.006 DCSync Credential Access
Adversaries may attempt to access credentials and other sensitive information by abusing a Windows Domain Controller's application programming interface (API)(Citation: Microsoft DRSR Dec 2017) (Citation: Microsoft GetNCCChanges) (Citati…
T1003.008 /etc/passwd and /etc/shadow Credential Access
Adversaries may attempt to dump the contents of <code>/etc/passwd</code> and <code>/etc/shadow</code> to enable offline password cracking.
T1006 Direct Volume Access Stealth
Adversaries may directly access a volume to bypass file access controls and file system monitoring.
T1007 System Service Discovery Discovery
Adversaries may try to gather information about registered local system services.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-49499Shared CWE-1270
CVE-2023-22644Shared CWE-1270
CVE-2023-2882Shared CWE-1270
CVE-2025-59698Shared CWE-1270
CVE-2023-30524Shared CWE-1270
CVE-2026-54593Shared CWE-1270

Affected Assets

Suse
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover flaws that produce incorrect security tokens before deployment.

Correct association and handling of security attributes directly governs generation of valid tokens used for authorization decisions.

Requiring documented, secure development processes and tools reduces the chance of implementing faulty token-generation logic.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-04 partial match
blocks

Verification of identity assertions can detect incorrect tokens but does not prevent flawed generation logic.

PR.PS-06 partial match
blocks

Secure SDLC practices directly reduce the chance of implementing incorrect token generation.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

A.8.24 governs the selection, strength, key management and deployment of cryptography to protect information per policy; it has no bearing on whether a security token generation mechanism produces correct (or incorrect) tokens that differentiate permitted actions.

blocks

Secure development lifecycle practices include requirements and reviews that prevent flawed token-generation logic.

blocks

Application security requirements explicitly call for correct token issuance and validation mechanisms.

prevents

Secure coding standards reduce the likelihood of implementation errors that produce incorrect tokens.

finds

Security testing in development can detect incorrect token generation before deployment.

References