Skip to content

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

Moderate severity GitHub Reviewed Published Mar 6, 2025 to the GitHub Advisory Database • Updated Mar 6, 2025

Package

maven org.jenkins-ci.main:jenkins-core (Maven)

Affected versions

< 2.492.2
>= 2.493, < 2.500

Patched versions

2.492.2
2.500

Description

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

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

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

References

Published by the National Vulnerability Database Mar 5, 2025
Published to the GitHub Advisory Database Mar 6, 2025
Reviewed Mar 6, 2025
Last updated Mar 6, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

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

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(12th percentile)

Weaknesses

CVE ID

CVE-2025-27623

GHSA ID

GHSA-rfh6-9r2q-98vf

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.