dbcve.org
Dimensions CmApplication · Microfocus

CVE-2023-32262

MEDIUM · 6.5 CVSS v3.1 Published 2023-07-19
Fix available
A fix is available. Upgrade to 0.9.3.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 allows attackers with Item/Configure permission to access and capture credentials they are not entitled to. See the following Jenkins security advisory for details: * https://www.jenkins.io/security/advisory/2023-06-14/ 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 · high confidence

This is an authorization bypass vulnerability in the Micro Focus Dimensions CM Plugin for Jenkins. The plugin fails to properly restrict access to stored credentials, allowing users with Item/Configure permission to access and capture credentials they are not entitled to. This enables credential theft by privileged but not fully authorized Jenkins users.

MitigationUpdate the Micro Focus Dimensions CM Plugin for Jenkins to the latest patched version. Additionally, review and restrict Item/Configure permissions to only necessary personnel and audit for any unauthorized credential access.

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.1

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
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 checks

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

  1. Identify if Micro Focus Dimensions CM Plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or inspect the $JENKINS_HOME/plugins directory for a folder named 'dimensionscm' or similar plugin naming convention.
    Affected if The plugin is present in the installed plugins list or filesystem.
  2. Determine the installed plugin version
    In Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab, locate the Micro Focus Dimensions CM plugin, and note the version column. Alternatively, inspect the plugin's manifest file ( MANIFEST.MF) inside the plugin .hpi file or the plugin folder.
    Affected if The installed version is 0.8.17 or higher, but lower than 0.9.3.1.
  3. Verify Item/Configure permission assignments
    Navigate to Jenkins > Manage Jenkins > Configure Global Security or inspect the $JENKINS_HOME/users directory for user configuration files. Review which users or groups are granted the 'Overall/Administer' or 'Item/Configure' permissions in the security matrix or project-based matrix.
    Affected if Users who should not have credential access are granted Item/Configure permission, and the vulnerable plugin version is installed.
  4. Check for stored credentials in job configurations
    Inspect saved job configurations that use the Dimensions CM plugin, looking for configured credentials in the job's configuration XML files under $JENKINS_HOME/jobs/<jobname>/config.xml or via the UI at Job > Configure.
    Affected if Jobs contain stored credentials configured for Dimensions CM integration.

You are affected if the Micro Focus Dimensions CM plugin versions 0.8.17 through 0.9.3.0 are installed and users with Item/Configure permission have access to credentials they should not see.

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.

dbcve · scoped
Upgrade available Upgrade to 0.9.3.1 or later
Fixed in 0.9.3.1
Interim mitigation

Update the Micro Focus Dimensions CM Plugin for Jenkins to the latest patched version. Additionally, review and restrict Item/Configure permissions to only necessary personnel and audit for any unauthorized credential access.

Recommended fix High confidence

Micro Focus Dimensions CM plugin version 0.9.3.1 or later

  1. 1. Navigate to Jenkins dashboard
  2. 2. Go to Manage Jenkins > Manage Plugins
  3. 3. Select the 'Installed' tab
  4. 4. Locate 'Micro Focus Dimensions CM' plugin in the list
  5. 5. If an update is available, check the plugin and click 'Update'
  6. 6. Alternatively, go to 'Available' tab and search for 'Micro Focus Dimensions CM'
  7. 7. Select the latest version (0.9.3.1 or later) and install
  8. 8. Restart Jenkins if required to complete the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dimensions Cm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32262 — 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-32262 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