CVE-2022-43423
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJenkins Compuware Source Code Download for Endevor, PDS, and ISPW Plugin 2.0.12 and earlier implements an agent/controller message that does not limit where it can be executed, allowing attackers able to control agent processes to obtain the values of Java system properties from the Jenkins controller process.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Jenkins Compuware Source Code Download plugin versions 2.0.12 and earlier implements an agent/controller message that can be executed on the Jenkins controller rather than being restricted to agent processes. Attackers who can control agent processes can exploit this to retrieve Java system properties from the Jenkins controller JVM, exposing sensitive configuration information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.0.13CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Compuware Source Code Download plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed, or list contents of $JENKINS_HOME/plugins/ directory for a folder starting with 'compuware-sourcedownload' or similar Compuware-related plugin nameAffected if The Compuware Source Code Download plugin is present in the Jenkins plugins directory or listed in the installed plugins
-
Determine the installed plugin versionCheck the plugin's MANIFEST.MF file within its plugin folder, or view the version column in Manage Jenkins > Manage Plugins > Installed tabAffected if The version is 2.0.12 or earlier (versions prior to 2.0.13 are affected)
-
Verify the plugin is enabled and loadedCheck Manage Jenkins > Manage Plugins > Installed tab to confirm the plugin status shows as 'Enabled' or 'Active', or check $JENKINS_HOME/plugins/<plugin>/META-INF/MANIFEST.MF for Bundle-ActivationPolicyAffected if The plugin is installed and enabled, making the vulnerable code available for exploitation
-
Check for configured agent nodes that could be controlledNavigate to Manage Jenkins > Manage Nodes, or inspect $JENKINS_HOME/nodes/ directory for configured agent configurationsAffected if Any agent nodes are configured and online, as an attacker who can control these agents can trigger the vulnerable message handler
The environment is affected if the Compuware Source Code Download plugin is installed with version 2.0.12 or earlier and is enabled, regardless of whether the plugin feature is actively used.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.0.13
Update the Compuware Source Code Download plugin to a version newer than 2.0.12. Additionally, restrict who can control Jenkins agent processes to limit the attack surface.
2.0.13
- Back up your Jenkins configuration and plugins directory before making changes
- Log in to Jenkins as an administrator
- Navigate to 'Manage Jenkins' > 'Manage Plugins'
- Go to the 'Updates' tab or 'Available' tab
- Locate 'Compuware Source Code Download for Endevor, PDS, and ISPW' in the plugin list
- Select the plugin and click 'Download now and install after restart' or 'Install'
- Wait for the plugin to download and install
- Restart Jenkins (or wait for the next scheduled restart if using zero-downtime)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43423 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-43423 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data