dbcve.org
Dimensions CmApplication · Microfocus

CVE-2023-32263

MEDIUM · 5.7 CVSS v3.1 Published 2023-07-19
Fix available
A fix is available. Upgrade to after 0.9.3 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
A potential vulnerability has been identified in the Micro Focus Dimensions CM Plugin for Jenkins. The vulnerability could be exploited to retrieve a login certificate if an authenticated user is duped into using an attacker-controlled Dimensions CM server. This vulnerability only applies when the Jenkins plugin is configured to use login certificate credentials. https://www.jenkins.io/security/advisory/2023-06-14/

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 · moderate confidence

The Micro Focus Dimensions CM Plugin for Jenkins contains a vulnerability that allows an authenticated user's login certificate to be intercepted when they connect to a malicious Dimensions CM server. An attacker controlling the server can harvest these credentials. This only affects configurations using login certificate authentication.

MitigationEnsure Jenkins users only connect to trusted, verified Dimensions CM servers. Review and validate all configured Dimensions CM server endpoints in the plugin configuration, and implement server certificate validation or pinning if available.

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
Dimensions CmApplication
Affected:>= 0.8.17, <= 0.9.3

CVSS 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Dimensions CM plugin is installed
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed and search for 'Dimensions CM' or 'Micro Focus Dimensions CM'. Alternatively, check the plugin directory on the Jenkins controller (typically $JENKINS_HOME/plugins/) for a dimensions-cm-plugin folder.
    Affected if The Micro Focus Dimensions CM plugin is present in Jenkins
  2. Check installed plugin version
    In Jenkins UI: Manage Jenkins > Manage Plugins > Installed > Micro Focus Dimensions CM plugin. Note the version displayed. Compare against the affected range: 0.8.17 through 0.9.3 (inclusive).
    Affected if The installed version is 0.8.17, 0.8.18, 0.8.19, 0.9.0, 0.9.1, 0.9.2, or 0.9.3
  3. Identify Dimensions CM server configurations
    In Jenkins, locate job configurations or global configurations that use the Dimensions CM plugin. Look for saved configurations or credentials that reference Dimensions CM servers. Check if any Dimensions CM server endpoint URLs are stored in job configurations or global tool configurations.
    Affected if Any Dimensions CM server connections are configured in Jenkins
  4. Determine authentication method in use
    Examine the Dimensions CM plugin configuration for the authentication type being used. Look specifically for 'login certificate' or certificate-based authentication settings in the plugin configuration panel for each configured server connection.
    Affected if Login certificate authentication is configured for any Dimensions CM server connection

A user is affected if the Dimensions CM plugin versions 0.8.17 through 0.9.3 are installed AND login certificate authentication is configured for at least one Dimensions CM server connection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 0.9.3
Interim mitigation

Ensure Jenkins users only connect to trusted, verified Dimensions CM servers. Review and validate all configured Dimensions CM server endpoints in the plugin configuration, and implement server certificate validation or pinning if available.

Fix this in Dimensions Cm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32263 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-32263 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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