Skip to content

GHSA-p34j-r3ch-c985 BIT-jenkins-2025-27622 CVE-2025-27622

Jenkins reveals encrypted values of secrets stored in agent configuration to users with Agent/Extended Read permission

Medium Maven
Severity
4.3 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.78%
Chance of exploitation in the next 30 days. Higher than 55.98% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-312 Cleartext Storage of Sensitive Information
Fix
2.500
Upgrade org.jenkins-ci.main:jenkins-core to this version or later

Description

Jenkins 2.499 and earlier, LTS 2.492.1 and earlier does not redact encrypted values of secrets when accessing config.xml of agents via REST API or CLI.

This allows attackers with Agent/Extended Read permission to view encrypted values of secrets.

Jenkins 2.500, LTS 2.492.2 redacts the encrypted values of secrets stored in agent config.xml accessed via REST API or CLI for users lacking Agent/Configure permission.

Affected versions

Maven

PackageVulnerableFixed in
org.jenkins-ci.main:jenkins-core
>= 2.493, < 2.500
2.500
org.jenkins-ci.main:jenkins-core
< 2.492.2
2.492.2

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.jenkins-ci.main:jenkins-core Maven → 2.500

maven
<dependency><groupId>org.jenkins-ci.main</groupId><artifactId>jenkins-core</artifactId><version>2.500</version></dependency>
gradle
implementation("org.jenkins-ci.main:jenkins-core:2.500")

Severity breakdown

CVSS 3.1 4.3

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Weakness

CWE-312: Cleartext Storage of Sensitive Information

The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.

How to prevent it
  • Implementation, System Configuration, Operation: When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to encrypt the data at rest. [REF-1297] [REF-1299] [REF-1301]
  • Implementation, System Configuration, Operation: In some systems/environments such as cloud, the use of "double encryption" (at both the software and hardware layer) might be required, and the developer might be solely responsible for both layers, instead of shared responsibility with the administrator of the broader system/environment.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-6f9g-cxwr-q5jr
Arbitrary file read vulnerability through the Jenkins CLI can lead to RCE
Critical Known exploited Also affects org.jenkins-ci.main:jenkins-core
GHSA-8pqx-3rxx-f5pm
Jenkins discloses project names via fingerprints
High Known exploited Also affects org.jenkins-ci.main:jenkins-core
GHSA-26wc-3wqp-g3rp
Deserialization of Untrusted Data in Jenkins
Critical Known exploited Also affects org.jenkins-ci.main:jenkins-core
CVE-2018-1000861
Deserialization of Untrusted Data in Jenkins
Critical Known exploited Also affects org.jenkins-ci.main:jenkins-core
GHSA-m6wv-wh8g-64xc
Jenkins does not encrypt secrets from POST config.xml submissions before storing them in job configurations
Medium Also affects org.jenkins-ci.main:jenkins-core
GHSA-93qh-vwrm-c5pw
Jenkins: Stored XSS vulnerability in node offline cause description
Medium Also affects org.jenkins-ci.main:jenkins-core
GHSA-92m7-4fpw-2wxm
Jenkins: Open Redirect phishing attacks possible via "from" parameter in "Delegate to servlet container"
Medium Also affects org.jenkins-ci.main:jenkins-core
GHSA-g28p-6mcc-v4rv
Jenkins exposes other users' timezone and view names to users with Overall/Read permission
Medium Also affects org.jenkins-ci.main:jenkins-core
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor