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
Copy file name to clipboardExpand all lines: docs/16.security_advisories/01.security_advisories/cve.md
+22-9Lines changed: 22 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,16 @@
1
-
# Sensitive information exposure in NeuVector manager container logs
1
+
# Security Advisories and CVEs
2
+
3
+
NeuVector is committed to informing the community of security issues. Below is a CVE reference list of published security advisories and CVEs (Common Vulnerabilities and Exposures) for issues we have resolved.
4
+
5
+
## CVE List
6
+
7
+
| ID | Description | Date | Resolution |
8
+
| :---- | :---- | :---- | :---- |
9
+
|[CVE-2025-8077](https://github.com/neuvector/neuvector/security/advisories/GHSA-8pxw-9c75-6w56)| For NeuVector deployment on the Kubernetes-based environment, the bootstrap password of the default admin user will be generated randomly and stored in a Kubernetes secret. The default admin will need to get the bootstrap password from the Kubernetes secret first and will be asked to change password after the first UI login is successful. | 25 Aug 2025 |[NeuVector v5.4.6](https://github.com/neuvector/neuvector/releases/tag/v5.4.6)|
10
+
|[CVE-2025-53884](https://github.com/neuvector/neuvector/security/advisories/GHSA-8ff6-pc43-jwv3)| NeuVector uses a cryptographically secure salt with the PBKDF2 algorithm instead of a simple hash to protect user passwords.For rolling upgrades from earlier versions, NeuVector recalculates and stores the new password hash only after each user’s next successful login. | 25 Aug 2025 |[NeuVector v5.4.6](https://github.com/neuvector/neuvector/releases/tag/v5.4.6)|
11
+
|[CVE-2025-54467](https://github.com/neuvector/neuvector/security/advisories/GHSA-w54x-xfxg-4gxq)| By default, NeuVector redacts process commands that contain the strings password,passwd, pwd, token, or key in security logs, syslog, enforcer debug logs, controller debug logs, webhooks, and support logs. Users can configure a Kubernetes ConfigMap to define custom regex patterns for additional process commands to redact. | 25 Aug 2025 |[NeuVector v5.4.6](https://github.com/neuvector/neuvector/releases/tag/v5.4.6)|
12
+
13
+
## Sensitive information exposure in NeuVector manager container logs
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
29
@@ -37,17 +49,18 @@ In the patched version, X-R-Sess is partially masked so that users can confirm w
37
49
38
50
Please consult the associated [Unsecured credentials](https://attack.mitre.org/techniques/T1552/) for further information about this category of attack.
39
51
40
-
### **Patches**
52
+
### Patches
41
53
42
54
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
55
44
-
### **Workarounds**
56
+
### Workarounds
45
57
46
58
No workarounds are currently available. Customers are advised to upgrade to a fixed version at their earliest convenience.
47
59
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).
60
+
## Questions and Support
53
61
62
+
* Contact the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy).
63
+
* Open an issue in the [NeuVector GitHub repository](https://github.com/neuvector/neuvector/issues/new/choose).
64
+
* References:
65
+
**[NeuVector Support Matrix](https://www.suse.com/suse-neuvector/support-matrix/all-supported-versions/neuvector-v-all-versions/)
66
+
**[Product Support Lifecycle](https://www.suse.com/lifecycle/#suse-security)
Copy file name to clipboardExpand all lines: versioned_docs/version-5.4/16.security_advisories/01.security_advisories/cve.md
+22-9Lines changed: 22 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,16 @@
1
-
# Sensitive information exposure in NeuVector manager container logs
1
+
# Security Advisories and CVEs
2
+
3
+
NeuVector is committed to informing the community of security issues. Below is a CVE reference list of published security advisories and CVEs (Common Vulnerabilities and Exposures) for issues we have resolved.
4
+
5
+
## CVE List
6
+
7
+
| ID | Description | Date | Resolution |
8
+
| :---- | :---- | :---- | :---- |
9
+
|[CVE-2025-8077](https://github.com/neuvector/neuvector/security/advisories/GHSA-8pxw-9c75-6w56)| For NeuVector deployment on the Kubernetes-based environment, the bootstrap password of the default admin user will be generated randomly and stored in a Kubernetes secret. The default admin will need to get the bootstrap password from the Kubernetes secret first and will be asked to change password after the first UI login is successful. | 25 Aug 2025 |[NeuVector v5.4.6](https://github.com/neuvector/neuvector/releases/tag/v5.4.6)|
10
+
|[CVE-2025-53884](https://github.com/neuvector/neuvector/security/advisories/GHSA-8ff6-pc43-jwv3)| NeuVector uses a cryptographically secure salt with the PBKDF2 algorithm instead of a simple hash to protect user passwords.For rolling upgrades from earlier versions, NeuVector recalculates and stores the new password hash only after each user’s next successful login. | 25 Aug 2025 |[NeuVector v5.4.6](https://github.com/neuvector/neuvector/releases/tag/v5.4.6)|
11
+
|[CVE-2025-54467](https://github.com/neuvector/neuvector/security/advisories/GHSA-w54x-xfxg-4gxq)| By default, NeuVector redacts process commands that contain the strings password,passwd, pwd, token, or key in security logs, syslog, enforcer debug logs, controller debug logs, webhooks, and support logs. Users can configure a Kubernetes ConfigMap to define custom regex patterns for additional process commands to redact. | 25 Aug 2025 |[NeuVector v5.4.6](https://github.com/neuvector/neuvector/releases/tag/v5.4.6)|
12
+
13
+
## Sensitive information exposure in NeuVector manager container logs
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
29
@@ -37,17 +49,18 @@ In the patched version, X-R-Sess is partially masked so that users can confirm w
37
49
38
50
Please consult the associated [Unsecured credentials](https://attack.mitre.org/techniques/T1552/) for further information about this category of attack.
39
51
40
-
### **Patches**
52
+
### Patches
41
53
42
54
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
55
44
-
### **Workarounds**
56
+
### Workarounds
45
57
46
58
No workarounds are currently available. Customers are advised to upgrade to a fixed version at their earliest convenience.
47
59
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).
60
+
## Questions and Support
53
61
62
+
* Contact the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy).
63
+
* Open an issue in the [NeuVector GitHub repository](https://github.com/neuvector/neuvector/issues/new/choose).
64
+
* References:
65
+
**[NeuVector Support Matrix](https://www.suse.com/suse-neuvector/support-matrix/all-supported-versions/neuvector-v-all-versions/)
66
+
**[Product Support Lifecycle](https://www.suse.com/lifecycle/#suse-security)
0 commit comments