From 3800d216ac8d5a6bd3e4a08e87ca9ff8a75e803c Mon Sep 17 00:00:00 2001 From: "advisory-database[bot]" <45398580+advisory-database[bot]@users.noreply.github.com> Date: Wed, 25 Sep 2024 15:30:31 +0000 Subject: [PATCH] Publish GHSA-622h-h2p8-743x --- .../10/GHSA-622h-h2p8-743x/GHSA-622h-h2p8-743x.json | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/advisories/github-reviewed/2023/10/GHSA-622h-h2p8-743x/GHSA-622h-h2p8-743x.json b/advisories/github-reviewed/2023/10/GHSA-622h-h2p8-743x/GHSA-622h-h2p8-743x.json index 9814c2c0bfd..58319d09c35 100644 --- a/advisories/github-reviewed/2023/10/GHSA-622h-h2p8-743x/GHSA-622h-h2p8-743x.json +++ b/advisories/github-reviewed/2023/10/GHSA-622h-h2p8-743x/GHSA-622h-h2p8-743x.json @@ -1,13 +1,13 @@ { "schema_version": "1.4.0", "id": "GHSA-622h-h2p8-743x", - "modified": "2023-10-06T20:43:52Z", + "modified": "2024-09-25T15:28:50Z", "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### For More Information \n\nView the NeuVector [Security Policy](https://github.com/neuvector/neuvector/security) \n\nGeneral NeuVector [documentation](https://open-docs.neuvector.com/) ", + "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": [ ], @@ -25,11 +25,14 @@ "introduced": "0" }, { - "fixed": "5.2.2" + "fixed": "0.0.0-20231003121714-be746957ee7c" } ] } - ] + ], + "database_specific": { + "last_known_affected_version_range": "< 0.0.0-20230930010431-57d107118e92" + } } ], "references": [