When a Java command with password parameters is executed and terminated by NeuVector for Process rule violation the password will appear in the NeuVector security event log.
When a Java command with password parameters is executed and terminated by NeuVector for Process rule violation the password will appear in the NeuVector security event log.
When a Java command with password parameters is executed and terminated by NeuVector for Process rule violation the password will appear in the NeuVector security event log.
### Impact
When a Java command with password parameters is executed and terminated by NeuVector for Process rule violation. For example,
```
java -cp /app ... Djavax.net.ssl.trustStorePassword=<Password>
```
The command with the password appears in the NeuVector security event. To prevent this, NeuVector uses the following default regular expression to detect and redact sensitive data from process commands:
```
(?i)(password|passwd|token)
```
Also, you can define custom patterns to redact by creating a Kubernetes ConfigMap. For example:
```
kubectl create configmap neuvector-custom-rules --from-file=secret-patterns.yaml -n neuvector
```
Sample `secret-patterns.yaml` content:
```
Pattern_list:
- (?i)(pawd|pword)
- (?i)(secret)
```
NeuVector uses the default and custom regex to decide whether the process command in a security event should be redacted.
**Note:** If numerous regular expression (regex) patterns are configured in the Kubernetes ConfigMap for extended coverage of sensitive data matching, it can significantly impact performance of NeuVector enforcer, particularly in scenarios involving large inputs or frequent execution. The primary factor contributing to performance issues in regex is backtracking, where the regex engine attempts various matching paths when a pattern doesn't immediately find a match.
### Patches
This issue is fixed in NeuVector version **5.4.6** and later.
### Workarounds
There is no workaround. Upgrade to a patched version of NeuVector as soon as possible.
### References
If you have any questions or comments about this advisory:
- Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.
- Open an issue in the [NeuVector](https://github.com/neuvector/neuvector/issues/new/choose) repository.
- 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).
NeuVector process with sensitive arguments lead to leakage in github.com/neuvector/neuvector.
NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.
(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)
The additional affected modules and versions are: github.com/neuvector/neuvector from v5.0.0 before v5.4.6.
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Sep 17, 2025, 12:29:36 PM
dateUpdated: Sep 17, 2025, 1:19:59 PM
1 related source bulletins · separate from aliases
openSUSE-SU-2025:15538-1: govulncheck-vulndb-0.0.20250908T141310-1.1 on GA media
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Deferred
Weakness classifications: CWE-522
Original publisher date fields
published: 2025-09-17T13:15:34.017
lastModified: 2026-06-17T09:40:09.260
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.