First published: Wed Apr 02 2025(Updated: )
Jenkins Cadence vManager Plugin 4.0.0-282.v5096a_c2db_275 and earlier stores Verisium Manager vAPI keys unencrypted in job `config.xml` files on the Jenkins controller as part of its configuration. These API keys can be viewed by users with Item/Extended Read permission or access to the Jenkins controller file system. Cadence vManager Plugin 4.0.1-286.v9e25a_740b_a_48 stores Verisium Manager vAPI keys encrypted once affected job configurations are saved again.
Credit: jenkinsci-cert@googlegroups.com
Affected Software | Affected Version | How to fix |
---|---|---|
Cadence vManager Plugin | <=4.0.0-282.v5096a_c2db_275 | |
maven/org.jenkins-ci.plugins:vmanager-plugin | <4.0.1 | 4.0.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-31724 is considered a moderate severity vulnerability due to the exposure of sensitive vAPI keys.
To mitigate CVE-2025-31724, update the Jenkins Cadence vManager Plugin to version 4.0.0-283.vxxxx or later.
CVE-2025-31724 affects users of the Jenkins Cadence vManager Plugin version 4.0.0-282.v5096a_c2db_275 and earlier.
The risks of CVE-2025-31724 include unauthorized access to Verisium Manager vAPI keys by users with Extended Read permission on the Jenkins controller.
In CVE-2025-31724, the Verisium Manager vAPI keys are stored unencrypted in job config.xml files on the Jenkins controller.