neuvector: Generation of Incorrect Security Tokens
CVE-2023-32188 is a critical-severity generation of incorrect security tokens vulnerability in neuvector from SUSE, with a CVSS 4.0 base score of 9.4 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 0.0.0-20231003121714-be746957ee7c as the first without the flaw, so updating neuvector to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.59% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update neuvector to 0.0.0-20231003121714-be746957ee7c or a later version.
- Update neuvector to 0.0.0-20231003121714-be746957ee7c or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| SUSE | neuvector | before 0.0.0-20231003121714-be746957ee7c | 0.0.0-20231003121714-be746957ee7c |
| Neuvector | neuvector | before 0.0.0-20231003121714-be746957ee7c | 0.0.0-20231003121714-be746957ee7c |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Attack requirements
- NoneThe attack does not depend on a particular deployment or configuration.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Confidentiality (vulnerable system)
- HighSerious loss of confidentiality on the vulnerable system.
- Integrity (vulnerable system)
- HighSerious loss of integrity on the vulnerable system.
- Availability (vulnerable system)
- HighSerious loss of availability on the vulnerable system.
- Confidentiality (other systems)
- HighSerious loss of confidentiality on systems beyond the vulnerable one.
- Integrity (other systems)
- HighSerious loss of integrity on systems beyond the vulnerable one.
- Availability (other systems)
- HighSerious loss of availability on systems beyond the vulnerable one.
Vector: CVSS: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. Scored by CNA (suse.de).
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Generation of Incorrect Security Tokens
The product implements a Security Token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Tokens generated in the system are incorrect.
How developers prevent this class of flaw
- Generation of Security Tokens should be reviewed for design inconsistency and common weaknesses. Security-Token definition and programming flow should be tested in pre-silicon and post-silicon testing.
More Generation of Incorrect Security Tokens vulnerabilities (CWE-1270)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in neuvector
- 8.8 High severity
- 8.8 High severity
- 7.3 High severity
- 8.8 High severity
- 8.6 High severity
- 9.9 Critical severity
Recent Generation of Incorrect Security Tokens vulnerabilities
- 9.8 Critical severity
Spotted an error? Tell us.