VulnerabilityPublished 4 Jul 2025Updated 12 Dec 2025

CVE-2024-9453: Jenkins openshift-sync-plugin · Sensitive Data in Logs

Affects Jenkins openshift-sync-pluginSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Jenkins openshift-sync-plugin	Affected =0	Fixed in–

AI-suggested

1. Immediately audit and restrict access to all centralized and local logs that may contain bearer tokens to trusted personnel only. 2. Implement log redaction or filtering mechanisms to prevent sensitive tokens from being recorded in logs. 3. Rotate bearer tokens frequently, reducing their validity period from one year to a shorter timeframe where possible. 4. Monitor logs and alert on any suspicious access patterns or token usage anomalies. 5. Apply the latest updates from Jenkins and Red Hat OpenShift projects once patches addressing this vulnerability are released. 6. Consider isolating Jenkins and OpenShift logging infrastructure to minimize exposure. 7. Educate DevOps and security teams about the risks of sensitive data in logs and enforce secure logging practices. 8. Use role-based access control (RBAC) to limit who can view logs containing sensitive information. 9. If feasible, implement encryption for logs at rest and in transit to protect sensitive data from unauthorized access.

Description

A vulnerability was found in Red Hat OpenShift Jenkins. The bearer token is not obfuscated in the logs and potentially carries a high risk if those logs are centralized when collected. The token is typically valid for one year. This flaw allows a malicious user to jeopardize the environment if they have access to sensitive information.

Impact

The primary impact of CVE-2024-9453 is the compromise of confidentiality due to exposure of bearer tokens in logs. If an attacker gains access to centralized logs containing these tokens, they can use them to authenticate as legitimate users or services, potentially leading to unauthorized access to OpenShift clusters and associated resources. This can result in data breaches, unauthorized deployments, or manipulation of workloads. Since the tokens are valid for up to one year, the window for exploitation is significant. Although integrity and availability are not directly impacted by this vulnerability, the unauthorized access enabled by token theft could lead to further attacks affecting those security properties. Organizations with centralized log management and extensive Jenkins-OpenShift integrations are at heightened risk. The medium CVSS score reflects the balance between ease of exploitation and the requirement for some level of access to logs.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 17:03 UTC

Technical details

References

Community reviews

Related threats