CVE-2023-32188: Github.com/neuvector/neuvector Remote Code Execution Vulnerability

CRITICAL
Advisory Identifier: GHSA-622h-h2p8-743x
CWE-1270
Published
Advisory Summary

CVE-2023-32188 is a CRITICAL remote code execution vulnerability (CWE-1270: Generation of Incorrect Security Tokens) affecting Github.com/neuvector/neuvector libraries in the Go ecosystem. The issue involves jwt token compromise can allow malicious actions including remote code execution (rce). Remediation is available by upgrading affected packages to version 0.0.0-20231003121714-be746957ee7c.

CVE-2023-32188 at a Glance

CVE Identifier CVE-2023-32188
GHSA Identifier GHSA-622h-h2p8-743x
Severity CRITICAL
CVSS v3.1 Base Score N/A
CWE Classification CWE-1270: Generation of Incorrect Security Tokens
Affected Product Github.com/neuvector/neuvector
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2023-32188

To remediate this vulnerability, upgrade all affected Github.com/neuvector/neuvector dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/neuvector/neuvector fixed: 0.0.0-20231003121714-be746957ee7c
Upgrade github.com/neuvector/neuvector to 0.0.0-20231003121714-be746957ee7c
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/neuvector/neuvector

How to Check if You Are Affected

To determine whether your application is affected by CVE-2023-32188, inspect your project dependencies for Github.com/neuvector/neuvector:

inspect dependencies for github.com/neuvector/neuvector

Analyze the terminal output to locate any version of Github.com/neuvector/neuvector in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.0.0-20231003121714-be746957ee7c), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-1270: Generation of Incorrect Security Tokens, where 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. In Github.com/neuvector/neuvector, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact 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. ### Patches Upgrade to NeuVector [version 5.2.2](https://open-docs.neuvector.com/releasenotes/5x) or later and latest Helm chart (2.6.3+). + In 5.2.2 the certificate for JWT-signing is created automatically by controller with validity of 90days and rotated automatically. + Use Helm-based deployment/upgrade to 5.2.2 to generate a unique certificate for Manager, REST API, ahd registry adapter. Helm based installation/upgrade is required in order to automatically generate certificates upon initial installation and each subsequent upgrade. + See [release notes](https://open-docs.neuvector.com/releasenotes/5x) for manual/yaml based deployment advice. + 5.2.2 also implements additional protections against possible RCE for the feature of custom compliance scripts. ### Workarounds Users can replace the Manager & Controller certificate manually by following the instructions in documented [here](https://open-docs.neuvector.com/configuration/console/replacecert). However, upgrading to 5.2.2 and replacing Manager/REST API certificate is recommended to provide additional security enhancements to prevent possible attempted exploit and resulting RCE. See [release notes](https://open-docs.neuvector.com/releasenotes/5x) for additional details. ### Credits Thank you to [Dejan Zelic](https://dejandayoff.com/) at [Offensive Security](https://www.offsec.com/) for responsibly reporting this vulnerability. ### For More Information View the NeuVector [Security Policy](https://github.com/neuvector/neuvector/security) General NeuVector [documentation](https://open-docs.neuvector.com/)

CVE-2023-32188 Affected Github.com/neuvector/neuvector Versions

1 component(s)
Fixed Versions:
0.0.0-20231003121714-be746957ee7c
Product / Package Ecosystem Affected Versions Fixed Version
github.com/neuvector/neuvector
Go
< 0.0.0-20231003121714-be746957ee7c
0.0.0-20231003121714-be746957ee7c

References

Frequently Asked Questions

What is CVE-2023-32188?
CVE-2023-32188 is a security vulnerability in Github.com/neuvector/neuvector involving JWT token compromise can allow malicious actions including Remote Code Execution (RCE) under CWE-1270: Generation of Incorrect Security Tokens.
Which Github.com/neuvector/neuvector versions are affected?
Affected versions include releases prior to 0.0.0-20231003121714-be746957ee7c across affected packages: github.com/neuvector/neuvector.
What version fixes CVE-2023-32188?
Upgrading to 0.0.0-20231003121714-be746957ee7c (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/neuvector/neuvector affected?
Yes, github.com/neuvector/neuvector is affected in releases prior to 0.0.0-20231003121714-be746957ee7c. Upgrade your dependency to 0.0.0-20231003121714-be746957ee7c or later.
What CWE is associated with CVE-2023-32188?
CVE-2023-32188 is classified under CWE-1270: 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 can I check Go dependencies for CVE-2023-32188?
Run the dependency tree command: 'inspect dependencies for github.com/neuvector/neuvector'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-622h-h2p8-743x",
  "modified" : "2024-10-16T17:05:17Z",
  "published" : "2023-10-06T20:43:52Z",
  "aliases" : [ "CVE-2023-32188" ],
  "summary" : "JWT token compromise can allow malicious actions including Remote Code Execution (RCE) ",
  "details" : "### Impact \n\nA 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. \n\n### Patches \n\nUpgrade to NeuVector [version 5.2.2](https://open-docs.neuvector.com/releasenotes/5x) or later and latest Helm chart (2.6.3+). \n+ In 5.2.2 the certificate for JWT-signing is created automatically by controller with validity of 90days and rotated automatically.\n+ Use Helm-based deployment/upgrade to 5.2.2 to generate a unique certificate for Manager, REST API, ahd registry adapter. Helm based installation/upgrade is required in order to automatically generate certificates upon initial installation and each subsequent upgrade. \n+ See [release notes](https://open-docs.neuvector.com/releasenotes/5x) for manual/yaml based deployment advice.\n+ 5.2.2 also implements additional protections against possible RCE for the feature of custom compliance scripts. \n\n### Workarounds \n\nUsers can replace the Manager & Controller certificate manually by following the instructions in documented [here](https://open-docs.neuvector.com/configuration/console/replacecert). However, upgrading to 5.2.2 and replacing Manager/REST API certificate is recommended to provide additional security enhancements to prevent possible attempted exploit and resulting RCE. See [release notes](https://open-docs.neuvector.com/releasenotes/5x) for additional details.\n\n### Credits \n\nThank you to [Dejan Zelic](https://dejandayoff.com/) at [Offensive Security](https://www.offsec.com/) for responsibly reporting this vulnerability. \n\n### For More Information \n\nView the NeuVector [Security Policy](https://github.com/neuvector/neuvector/security) \n\nGeneral NeuVector [documentation](https://open-docs.neuvector.com/) ",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/neuvector/neuvector"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.0.0-20231003121714-be746957ee7c"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "< 0.0.0-20230930010431-57d107118e92"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/neuvector/neuvector/security/advisories/GHSA-622h-h2p8-743x"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2023-32188"
  }, {
    "type" : "WEB",
    "url" : "https://bugzilla.suse.com/show_bug.cgi?id=CVE-2023-32188"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/neuvector/neuvector"
  }, {
    "type" : "WEB",
    "url" : "https://open-docs.neuvector.com/releasenotes/5x"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-1270" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2023-10-06T20:43:52Z",
    "nvd_published_at" : "2024-10-16T09:15:03Z"
  }
}