CVE-2022-41252VulnerabilityPublished 21 Sep 2022Updated 28 May 2025

CVE-2022-41252: Jenkins CONS3RT Plugin · Vulnerability

Affects Jenkins CONS3RT PluginSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.3Medium

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

EPSS: 0.6% chance of exploitation in 30 days – higher than 51% 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: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

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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
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 21 Sep 2022
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 2026-10-25.

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 project Jenkins CONS3RT Plugin	Affected <=1.0.0	Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should: 1) Review and tighten Jenkins permission schemes to ensure that only trusted users have Overall/Read permissions, minimizing exposure to untrusted or low-privilege users. 2) Monitor and audit Jenkins user activities to detect unusual enumeration or access patterns related to credentials. 4) Implement network segmentation and access controls to restrict Jenkins access to trusted networks and users. 5) Employ credential vaulting solutions external to Jenkins where possible, reducing reliance on Jenkins-stored credentials. 6) Educate Jenkins administrators and developers about the risks of excessive permissions and the importance of least privilege principles. 7) Regularly review Jenkins plugins for security advisories and apply updates promptly to reduce exposure to known vulnerabilities.

Description

Missing permission checks in Jenkins CONS3RT Plugin 1.0.0 and earlier allows users with Overall/Read permission to enumerate credentials ID of credentials stored in Jenkins.

Impact

For European organizations, this vulnerability poses a moderate risk primarily in environments where Jenkins is used extensively for continuous integration and deployment pipelines, especially in sectors with sensitive or regulated data such as finance, healthcare, and critical infrastructure. The ability to enumerate credential IDs can facilitate reconnaissance that may lead to targeted attacks, including attempts to exploit other vulnerabilities or social engineering attacks to obtain credential secrets. While the vulnerability itself does not expose credential secrets or allow modification, it lowers the barrier for attackers to identify valuable credentials, potentially accelerating lateral movement or privilege escalation within the network. Organizations with large Jenkins deployments or multi-tenant Jenkins environments where users have varying permission levels are particularly at risk. Given the widespread use of Jenkins in European enterprises and public sector organizations, the vulnerability could be leveraged to compromise build pipelines, leading to supply chain risks or unauthorized code deployment if combined with other vulnerabilities or misconfigurations.

CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jul 2025, 09:10 UTC

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats