CVE-2023-25721: Veracode scan Veracode Scan Jenkins Plugin Vulnerable Vulnerability

MODERATE
Advisory Identifier: GHSA-c4jr-vjm4-27hq
CVSS 4.4
CWE-532
Published
Advisory Summary

CVE-2023-25721 is a MODERATE (CVSS 4.4) veracode scan jenkins plugin vulnerable vulnerability (CWE-532: Insertion of Sensitive Information into Log File) affecting Veracode scan libraries in the Maven ecosystem. The issue involves veracode scan jenkins plugin vulnerable to information disclosure. Remediation is available by upgrading affected packages to version 23.3.19.0.

CVE-2023-25721 at a Glance

CVE Identifier CVE-2023-25721
GHSA Identifier GHSA-c4jr-vjm4-27hq
Severity MODERATE
CVSS v3.1 Base Score 4.4
CWE Classification CWE-532: Insertion of Sensitive Information into Log File
Affected Product Veracode scan
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 4.4

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required High (PR:H)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2023-25721

To remediate this vulnerability, upgrade all affected Veracode scan dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

com.veracode.jenkins:veracode-scan fixed: 23.3.19.0
<dependency>
    <groupId>com.veracode.jenkins</groupId>
    <artifactId>veracode-scan</artifactId>
    <version>23.3.19.0</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=com.veracode.jenkins

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2023-25721, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=com.veracode.jenkins

Analyze the terminal output to locate any version of Veracode scan in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 23.3.19.0), your application is affected.

Note: The mvn dependency:tree -Dincludes=com.veracode.jenkins command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-532: Insertion of Sensitive Information into Log File, where the product writes sensitive information to a log file. In Veracode scan, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

Veracode Scan Jenkins Plugin before 23.3.19.0 is vulnerable to information disclosure of proxy credentials in job logs under specific configurations. Users are potentially affected if they: - are using Veracode Scan Jenkins Plugin prior to 23.3.19.0 - AND have configured Veracode Scan to run on remote agent jobs - AND have enabled the "Connect using proxy" option - AND have configured the proxy settings with proxy credentials - AND a Jenkins admin has enabled debug in global system settings. By default, even in this configuration only the job owner or Jenkins admin can view the job log.

CVE-2023-25721 Affected Veracode scan Versions

1 component(s)
Fixed Versions:
23.3.19.0
Product / Package Ecosystem Affected Versions Fixed Version
com.veracode.jenkins:veracode-scan
Maven
< 23.3.19.0
23.3.19.0

References

Frequently Asked Questions

What is CVE-2023-25721?
CVE-2023-25721 is a security vulnerability in Veracode scan involving Veracode Scan Jenkins Plugin vulnerable to information disclosure under CWE-532: Insertion of Sensitive Information into Log File.
Which Veracode scan versions are affected?
Affected versions include releases prior to 23.3.19.0 across affected packages: com.veracode.jenkins:veracode-scan.
What version fixes CVE-2023-25721?
Upgrading to 23.3.19.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is veracode-scan affected?
Yes, com.veracode.jenkins:veracode-scan is affected in releases prior to 23.3.19.0. Upgrade your dependency to 23.3.19.0 or later.
What is the CVSS score of CVE-2023-25721?
CVE-2023-25721 has a CVSS v3.1 base score of 4.4 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2023-25721?
CVE-2023-25721 is classified under CWE-532: Insertion of Sensitive Information into Log File (The product writes sensitive information to a log file.).
How can I check Maven dependencies for CVE-2023-25721?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=com.veracode.jenkins'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-c4jr-vjm4-27hq",
  "modified" : "2023-04-05T19:40:36Z",
  "published" : "2023-03-28T21:30:20Z",
  "aliases" : [ "CVE-2023-25721" ],
  "summary" : "Veracode Scan Jenkins Plugin vulnerable to information disclosure",
  "details" : "Veracode Scan Jenkins Plugin before 23.3.19.0 is vulnerable to information disclosure of proxy credentials in job logs under specific configurations.\n\nUsers are potentially affected if they:\n- are using Veracode Scan Jenkins Plugin prior to 23.3.19.0\n- AND have configured Veracode Scan to run on remote agent jobs\n- AND have enabled the \"Connect using proxy\" option\n- AND have configured the proxy settings with proxy credentials\n- AND a Jenkins admin has enabled debug in global system settings.\n\nBy default, even in this configuration only the job owner or Jenkins admin can view the job log.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "com.veracode.jenkins:veracode-scan"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "23.3.19.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2023-25721"
  }, {
    "type" : "WEB",
    "url" : "https://community.veracode.com/s/spotlight/frequently-asked-questions-for-cve-2023-25721-and-cve-2023-25722-MCFT34TH6OGRFR7F7JGDQQP4TNZE"
  }, {
    "type" : "WEB",
    "url" : "https://docs.veracode.com/updates/r/c_all_int#veracode-jenkins-plugin-233190"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/jenkinsci/veracode-scan-plugin"
  }, {
    "type" : "WEB",
    "url" : "https://veracode.com"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-532" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2023-04-05T19:40:36Z",
    "nvd_published_at" : "2023-03-28T20:15:00Z"
  }
}