You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
***NVSHAS-9971**: NV UI about `Get Bootstrap Password`.
46
+
***NVSHAS-9975**: [Manager] TypeError: `this.mousemoveListener` is not a function is observed on the NV GUI.
47
+
***NVSHAS-9986**: Process profile rules and File access rules cannot be edited and removed in Federated policy group view.
48
+
***NVSHAS-9988**: UI: Group pages is not showing all groups when more than 2k groups present.
49
+
***NVSHAS-9991**: The group `nv.gatekeeper-controller-manager.openshift-azure-guardrails` is missing from UI.
50
+
***NVSHAS-9993**: Replace md5 by sha256.
51
+
***NVSHAS-9994**: The enforcer pod keeps restarting.
52
+
***NVSHAS-9996**: NeuVector Helm chart should allow non-privileged mode of enforcer pods.
53
+
***NVSHAS-9998**: Cannot export group from Neuvector federated master.
54
+
***NVSHAS-10000**: Upgrade NV to BCI 15.7.
55
+
***NVSHAS-10003**: Reload page does not work on standalone NV page while a Rancher UI is opening.
56
+
***NVSHAS-10008**: Registry Scan - View menu is broken for Scanned Image.
57
+
***NVSHAS-10010**: TCP SYN Flood blocks ingress causing complete ingress traffic being blocked.
58
+
14
59
#### 5.4.4 May 2025
15
60
16
61
##### New Features:
@@ -134,7 +179,7 @@ In the NeuVector 5.4.2 release, support is discontinued for deployments using th
134
179
135
180
Please create and configure internal certificates from the scanner for the controller, enforcer, and registry-adapter to achieve a rolling update without losing data. It is still recommended to take a backup of your configuration before upgrading.
136
181
137
-
The following steps are only needed if your deployment uses a `.yaml` file. Upgrading using Helm does not need these additional steps due to the internal certificates getting created by default via the following flags: `internal.autoGenerateCert` and `internal.autoRotateCert`.
182
+
The following steps are only needed if your deployment uses a `.yaml` file. Upgrading using Helm does not need these additional steps due to the internal certificates getting created by default via the following flags: `internal.autoGenerateCert` and `internal.autoRotateCert`.
138
183
139
184
```shell
140
185
docker run -it --entrypoint=bash neuvector/scanner:3.654 -c "cat /etc/neuvector/certs/internal/ca.cert"> ca.crt
**CWE:**[CWE-532: Insertion of Sensitive Information into Log File](https://cwe.mitre.org/data/definitions/532)
6
+
7
+
**Affected Versions**
8
+
9
+
* All versions earlier than `5.0.0`
10
+
* Versions from `5.0.0` up to and including `5.4.4`
11
+
12
+
**Fixed version: `5.4.5`**
13
+
14
+
### **Impact**
15
+
16
+
A vulnerability has been identified in the NeuVector version up to and including `5.4.4`, where sensitive information is leaked into the manager container’s log. The listed fields can be caught in the log:
17
+
18
+
| Field | Field Description | Where it Appears | Reproduction | Environment |
19
+
| :---- | :---- | :---- | :---- | :---- |
20
+
|`X-R-Sess`| Rancher’s session token for single sign on token | Request header | Log in via Rancher UI and access NeuVector SSO | Rancher with NeuVector SSO |
21
+
|`personal_access_token`| The Github / Azure DevOps token | Request body | Submit remote repository config under *Configuration \> Settings*| NeuVector |
22
+
|`token1.token`| NeuVector user’s session token | Response body | Send GET request through NeuVector web server’s API: `https://<neuvector ui’s url>/user?name=<username>`| NeuVector |
23
+
|`rekor_public_key`, `root_cert`, `sct_public_key`| Rekor public key, Root certificate, Signed certificate timestamp(SCT) Public Key in private root of trust | Request body | Create/update private root of trust from Sigstore page | NeuVector |
24
+
| public\_key | Verifier’s public key | Request body | Create/update verifier in Sigstore page | NeuVector |
25
+
26
+
:::note
27
+
**Note:** NeuVector installations not using the single sign-on integration with Rancher Manager, and does not have Remote Repository Configuration enabled, are not affected by this issue.
28
+
:::
29
+
30
+
In the patched version, X-R-Sess is partially masked so that users can confirm what it is being used while still keeping it safe for consumption. The log which includes `personal_access_token`, `token`, `rekor_public_key`, `root_cert`, `sct_public_key`, `public key` are removed, as the request body is not mandatory in the log.
31
+
32
+
:::note
33
+
* The severity of the vulnerability depends on your logging strategy.
34
+
***Local logging (default)**: Limits exposure of impact.
35
+
***External logging**: Vulnerability’s severity increases, the impact depends on security measures implemented at the external log collector level.
36
+
* The final impact severity for confidentiality, integrity and availability is dependent on the permissions that the leaked credentials have on their own services.
37
+
38
+
Please consult the associated [Unsecured credentials](https://attack.mitre.org/techniques/T1552/) for further information about this category of attack.
39
+
40
+
### **Patches**
41
+
42
+
Patched versions include release `5.4.5` and above. Users are advised to rotate the GitHub token used in Remote Repository Configuration once they have upgraded to a fixed version.
43
+
44
+
### **Workarounds**
45
+
46
+
No workarounds are currently available. Customers are advised to upgrade to a fixed version at their earliest convenience.
47
+
48
+
If you have any questions or comments about this advisory:
49
+
50
+
* Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.
51
+
* Open an issue in the [NeuVector](https://github.com/neuvector/neuvector/issues/new/choose) repository.
52
+
* Verify with our [support matrix](https://www.suse.com/suse-neuvector/support-matrix/all-supported-versions/neuvector-v-all-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/#suse-security).
0 commit comments