When Jenkins Structs Plugin 337.v1b_04ea_4df7c8 and earlier fails to configure a build step, it logs a warning message containing diagnostic information that may contain secrets passed as step parameters, potentially resulting in accidental exposure of secrets through the default system log.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - When Jenkins Structs Plugin 337.v1b_04ea_4df7c8 and earlier fails to configure a build step, it logs a
    warning message containing diagnostic information that may contain secrets passed as step parameters,
    potentially resulting in accidental exposure of secrets through the default system log. (CVE-2024-39458)

According to their self-reported version numbers, the version of Jenkins plugins running on the remote web server are affected by multiple vulnerabilities:

  - Low Structs Plugin provides utility functionality used, e.g., in Pipeline to instantiate and configure     build steps, typically before their execution. When Structs Plugin 337.v1b_04ea_4df7c8 and earlier fails     to configure a build step, it logs a warning message containing diagnostic information that may contain     secrets passed as step parameters. This can result in accidental exposure of secrets through the default     system log. Structs Plugin 338.v848422169819 inspects the types of actual parameters before logging these     warning messages, and limits detailed diagnostic information to FINE level log messages if secrets are     involved. These log messages are not displayed in the default Jenkins system log. (CVE-2024-39458)

  - Medium When creating secret file credentials Plain Credentials Plugin 182.v468b_97b_9dcb_8 and earlier     attempts to decrypt the content of the file to check if it constitutes a valid encrypted secret. In rare     cases the file content matches the expected format of an encrypted secret, and the file content will be     stored unencrypted (only Base64 encoded) on the Jenkins controller file system. These credentials can be     viewed by users with access to the Jenkins controller file system (global credentials) or with     Item/Extended Read permission (folder-scoped credentials). Secret file credentials stored unencrypted are     unusable, as they would be decrypted during their use. Any successfully used secret file credentials are     therefore unaffected. Plain Credentials Plugin 183.va_de8f1dd5a_2b_ no longer attempts to decrypt the     content of the file when creating secret file credentials. (CVE-2024-39459)

  - Medium Bitbucket Branch Source Plugin 886.v44cf5e4ecec5 and earlier prints the Bitbucket OAuth access     token as part of the Bitbucket URL in the build log in some cases. Bitbucket Branch Source Plugin     887.va_d359b_3d2d8d does not include the Bitbucket OAuth access token as part of the Bitbucket URL in the     build log. (CVE-2024-39460)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Type	Severity
420470	SCA: security update for org.jenkins-ci.plugins:structs (GHSA-xfx3-cr74-x3cv)	Tenable Cloud Security	SCA Checks	Local	low
420470	SCA: security update for org.jenkins-ci.plugins:structs (GHSA-xfx3-cr74-x3cv)	Tenable Self-Hosted Container Security	SCA Checks	Local	low
201047	Jenkins plugins Multiple Vulnerabilities (2024-06-26)	Nessus	CGI abuses	Combined	medium

Detections

Analytics

CVE-2024-39458

low

Tenable Plugins

low

low

medium