Byteguard Build Actions
Monthly
Cleartext exposure of API tokens in the Jenkins ByteGuard Build Actions Plugin 1.0 allows any authenticated Jenkins user with permission to view a job's configuration form to read tokens that should have been masked. Because the plugin renders the token value directly in the configuration form instead of substituting a masked placeholder, an actor who can already reach that page can simply copy the credential; the assessed vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) confirms a confidentiality-only, low-severity impact with no integrity or availability effect. EPSS is 0.17% (6th percentile), no public exploit code or CISA KEV entry was identified at time of analysis, and the practical exposure is bounded by the requirement for a valid Jenkins account holding configuration-read rights on the affected job.
Cleartext storage of external-service API tokens by the Jenkins ByteGuard Build Actions Plugin 1.0 lets anyone with Item/Extended Read permission on an affected job - or read access to the Jenkins controller filesystem - recover those tokens directly from job config.xml. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) confirms this is a low-privileged, network-reachable confidentiality-only issue: authentication requirements are low-privileged (PR:L), so an anonymous attacker cannot reach the token without first obtaining Extended Read or host-level file access, and impact is confined to whichever external service the leaked token authenticates to. EPSS is 0.17% (6th percentile) and no public exploit identified at time of analysis; this is a genuine but low-priority weakness that also depends on the non-default condition that the plugin is deployed with API tokens actually configured.
Cleartext exposure of API tokens in the Jenkins ByteGuard Build Actions Plugin 1.0 allows any authenticated Jenkins user with permission to view a job's configuration form to read tokens that should have been masked. Because the plugin renders the token value directly in the configuration form instead of substituting a masked placeholder, an actor who can already reach that page can simply copy the credential; the assessed vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) confirms a confidentiality-only, low-severity impact with no integrity or availability effect. EPSS is 0.17% (6th percentile), no public exploit code or CISA KEV entry was identified at time of analysis, and the practical exposure is bounded by the requirement for a valid Jenkins account holding configuration-read rights on the affected job.
Cleartext storage of external-service API tokens by the Jenkins ByteGuard Build Actions Plugin 1.0 lets anyone with Item/Extended Read permission on an affected job - or read access to the Jenkins controller filesystem - recover those tokens directly from job config.xml. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) confirms this is a low-privileged, network-reachable confidentiality-only issue: authentication requirements are low-privileged (PR:L), so an anonymous attacker cannot reach the token without first obtaining Extended Read or host-level file access, and impact is confined to whichever external service the leaked token authenticates to. EPSS is 0.17% (6th percentile) and no public exploit identified at time of analysis; this is a genuine but low-priority weakness that also depends on the non-default condition that the plugin is deployed with API tokens actually configured.