Compuware Source Code Download For Endevor\, Pds\, And IspwApplication · Jenkins
CVE-2022-36896
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 · uneditedA missing permission check in Jenkins Compuware Source Code Download for Endevor, PDS, and ISPW Plugin 2.0.12 and earlier allows attackers with Overall/Read permission to enumerate hosts and ports of Compuware configurations and credentials IDs of credentials stored in Jenkins.
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 confidenceThis is an information disclosure vulnerability in the Jenkins Compuware Source Code Download plugin where API endpoints lack proper permission checks. Attackers with basic Overall/Read permission (the lowest privilege level in Jenkins) can access sensitive configuration data including Compuware server hosts, ports, and credential IDs stored in Jenkins' credentials store.
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
Compuware Source Code Download For Endevor\, Pds\, And IspwApplication
<= 2.0.12CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 installedGo to Jenkins Manage Jenkins > Manage Plugins > Installed tab and search for 'Compuware Source Code Download' or inspect the plugin directory $JENKINS_HOME/plugins for compuware-scd or similar plugin folderAffected if Plugin is installed and appears in the Manage Plugins list
-
Determine the installed plugin versionIn Manage Jenkins > Manage Plugins > Installed tab, locate the Compuware Source Code Download plugin and note the version number displayed in the version columnAffected if Version is 2.0.12 or lower (any version up to and including 2.0.12)
-
Check if plugin has active server configurationsNavigate to the plugin configuration page (typically under Manage Jenkins > Configure System > Compuware Source Code Download or similar) and look for configured Compuware server connections with hostnames and portsAffected if Any Compuware server host/port configurations exist in the plugin settings
-
Verify if credentials are stored in Jenkins for this pluginGo to Manage Jenkins > Manage Credentials and review credentials scoped to the Jenkins instance, looking for any Compuware-related credential entries (often identified by credential kind or description)Affected if Any Compuware-related credentials exist in the Jenkins credentials store
-
Review Overall/Read permission assignmentGo to Manage Jenkins > Manage Users and then check People or Access Matrix to see which users or groups have Overall/Read permission enabledAffected if Any untrusted or unexpected users have Overall/Read permission granted
Environment is affected if the Compuware Source Code Download plugin version 2.0.12 or lower is installed AND has server configurations or credentials configured, especially if users beyond trusted administrators have Overall/Read access.
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.
From vendor dataUpgrade to Compuware Source Code Download plugin version 2.0.13 or later which includes proper permission checks. If immediate upgrade is not possible, review access controls and consider restricting Overall/Read permission to only trusted users.
Fix this in Compuware Source Code Download For Endevor\, Pds\, And Ispw
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36896 — 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-36896 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