Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2022-43427: Vulnerability in Jenkins project Jenkins Compuware Topaz for Total Test Plugin

0
Medium
VulnerabilityCVE-2022-43427cvecve-2022-43427
Published: Wed Oct 19 2022 (10/19/2022, 00:00:00 UTC)
Source: CVE
Vendor/Project: Jenkins project
Product: Jenkins Compuware Topaz for Total Test Plugin

Description

Jenkins Compuware Topaz for Total Test Plugin 2.4.8 and earlier does not perform permission checks in several HTTP endpoints, allowing attackers with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins.

AI-Powered Analysis

AILast updated: 07/05/2025, 04:27:30 UTC

Technical Analysis

CVE-2022-43427 is a medium-severity vulnerability affecting the Jenkins Compuware Topaz for Total Test Plugin version 2.4.8 and earlier. The vulnerability arises because the plugin does not enforce proper permission checks on several HTTP endpoints. Specifically, attackers who have Overall/Read permission within Jenkins can exploit this flaw to enumerate credential IDs stored in Jenkins. This means that while the attacker cannot directly access the credential secrets, they can obtain identifiers for credentials, which could be leveraged in further attacks such as targeted phishing, social engineering, or privilege escalation attempts. The vulnerability is classified under CWE-862 (Missing Authorization), indicating a failure to properly restrict access to sensitive resources. The CVSS v3.1 base score is 4.3, reflecting a network attack vector with low complexity, requiring privileges (Overall/Read), no user interaction, and resulting in limited confidentiality impact without affecting integrity or availability. There are no known exploits in the wild as of the publication date, and no official patches are linked in the provided data, suggesting that remediation may require manual updates or configuration changes. This vulnerability is significant in environments where Jenkins is used for continuous integration and delivery (CI/CD) pipelines, especially where sensitive credentials are stored and managed within Jenkins. Attackers with read access could gain intelligence about credential identifiers, potentially aiding in lateral movement or further exploitation within the infrastructure.

Potential Impact

For European organizations, the impact of CVE-2022-43427 can be notable, particularly in sectors heavily reliant on automated software development pipelines such as finance, telecommunications, manufacturing, and government agencies. The ability to enumerate credential IDs could facilitate targeted attacks against critical infrastructure or intellectual property by enabling attackers to identify valuable credentials for further exploitation. Although the vulnerability does not directly expose credential secrets or allow modification, the information disclosure can aid attackers in crafting more effective social engineering or privilege escalation attacks. Organizations with large Jenkins deployments or those integrating Compuware Topaz for Total Test Plugin in their DevOps workflows may face increased risk. Additionally, compliance requirements under GDPR and other European data protection regulations could be implicated if credential enumeration leads to broader breaches or unauthorized access. The medium severity rating suggests that while immediate damage may be limited, the vulnerability could serve as a stepping stone in multi-stage attacks, increasing the overall risk posture of affected organizations.

Mitigation Recommendations

To mitigate CVE-2022-43427, European organizations should take several specific steps beyond generic advice: 1) Immediately audit Jenkins instances to identify usage of the Compuware Topaz for Total Test Plugin version 2.4.8 or earlier. 2) Restrict Overall/Read permissions to only trusted users, minimizing the attack surface by enforcing the principle of least privilege. 3) If possible, upgrade the plugin to a version where this vulnerability is fixed; if no patch is available, consider disabling or removing the plugin until a secure version is released. 4) Implement network segmentation and access controls to limit exposure of Jenkins HTTP endpoints to internal, trusted networks only. 5) Monitor Jenkins logs and HTTP endpoint access for unusual enumeration activity or unauthorized access attempts. 6) Educate DevOps and security teams about the risks of credential enumeration and enforce strict credential management policies, including regular credential rotation and use of credential vaults external to Jenkins. 7) Consider integrating Jenkins with centralized identity and access management (IAM) solutions to better control and audit permissions. These targeted actions will help reduce the risk posed by this vulnerability in operational environments.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
jenkins
Date Reserved
2022-10-18T00:00:00.000Z
Cisa Enriched
true
Cvss Version
3.1
State
PUBLISHED

Threat ID: 682d9818c4522896dcbd80c3

Added to database: 5/21/2025, 9:08:40 AM

Last enriched: 7/5/2025, 4:27:30 AM

Last updated: 2/7/2026, 6:18:17 PM

Views: 45

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats