Cyber 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.0048 39th percentile
Risk Priority 40 floored blend · peak EPSS

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 Forge Web Credentials (T1606); ranked at the 39th 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)
CWE-1270

Related Threats

MITRE ATT&CK Enterprise Techniques

T1606 Forge Web Credentials Credential Access
Adversaries may forge credential materials that can be used to gain access to web applications or Internet services.
attack.mitre.org →
T1606.002 SAML Tokens Credential Access
An adversary may forge SAML tokens with any permissions claims and lifetimes if they possess a valid SAML token-signing certificate.
attack.mitre.org →
T1134 Access Token Manipulation Stealth
Adversaries may modify access tokens to operate under a different user or system security context to perform actions and bypass access controls.
attack.mitre.org →
T1550 Use Alternate Authentication Material Lateral Movement
Adversaries may use alternate authentication material, such as password hashes, Kerberos tickets, and application access tokens, in order to move laterally within an environment and bypass normal system access controls.
attack.mitre.org →
T1606.001 Web Cookies Credential Access
Adversaries may forge web cookies that can be used to gain access to web applications or Internet services.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-2882Shared CWE-1270
CVE-2023-22644Shared CWE-1270
CVE-2023-30524Shared CWE-1270
CVE-2025-59698Shared CWE-1270
CVE-2026-49499Shared 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

SA-11 Developer Testing and Evaluation good match

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

AC-16 Security and Privacy Attributes partial match

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

SA-15 Development Process, Standards, and Tools partial match

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 mostly match
degrades

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

PR.PS-06 mostly match
prevents

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.

A.8.29 Security testing in development and acceptance mostly match
finds

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

A.8.24 Use of cryptography partial match
prevents

Proper use of cryptography ensures tokens are generated with correct algorithms, keys and entropy.

A.8.25 Secure development life cycle partial match
prevents

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

A.8.26 Application security requirements partial match
prevents

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

A.8.28 Secure coding partial match
prevents

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

A.8.5 Secure authentication partial match
prevents

Secure authentication mechanisms directly govern the correct generation and validation of security tokens.

References