GHSA-622h-h2p8-743x: JWT token compromise can allow malicious actions including Remote Code Execution (RCE)

1. GitHub Advisory Database
2. GitHub Reviewed
3. CVE-2023-32188

JWT token compromise can allow malicious actions including Remote Code Execution (RCE)

Critical severity GitHub Reviewed Published Oct 6, 2023 in neuvector/neuvector • Updated Oct 6, 2023

Package

gomod github.com/neuvector/neuvector (Go)

Affected versions

< 5.2.2

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 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 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. 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 for additional details.

For More Information

View the NeuVector Security Policy

General NeuVector documentation

References

• GHSA-622h-h2p8-743x
• https://open-docs.neuvector.com/releasenotes/5x

Published to the GitHub Advisory Database

Oct 6, 2023