dbcve.org
View ClonerApplication · Jenkins

CVE-2023-24450

MEDIUM · 6.5 CVSS v3.1 Published 2023-01-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Jenkins view-cloner Plugin 1.1 and earlier stores passwords unencrypted in job config.xml files on the Jenkins controller where they can be viewed by users with Extended Read permission, or access to the Jenkins controller file system.

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

The view-cloner Plugin for Jenkins versions 1.1 and earlier stores passwords in plaintext within job configuration files (config.xml). These unencrypted credentials are accessible to users with Extended Read permission on jobs, or to anyone with direct filesystem access to the Jenkins controller.

MitigationIdentify and remove or re-encrypt stored passwords in job config.xml files affected by the view-cloner plugin, and upgrade to a patched version of the plugin once available, or remove the plugin if unused.

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
View ClonerApplication
Affected:= 1.0= 1.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. Check if View Cloner plugin is installed
    Go to Manage Jenkins > Manage Plugins > Installed tab and search for 'view-cloner' or 'View Cloner'. Alternatively, check the $JENKINS_HOME/plugins directory for a view-cloner folder.
    Affected if The View Cloner plugin is present on the Jenkins instance.
  2. Determine the installed plugin version
    In Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab, find View Cloner, and note the version shown. Or read the $JENKINS_HOME/plugins/view-cloner/META-INF/MANIFEST.MF file for the Plugin-Version attribute.
    Affected if The version is 1.0 or 1.1 (or any version earlier than the patched release).
  3. Identify jobs that used the View Cloner plugin
    Review job histories or look for jobs created or modified around the time the View Cloner plugin was used. Check job directories in $JENKINS_HOME/jobs/ for config.xml files that may contain cloned view configurations with stored credentials.
    Affected if There are jobs whose config.xml files were created or modified using the View Cloner plugin.
  4. Search for plaintext passwords in job config.xml files
    On the Jenkins controller filesystem, search through config.xml files in $JENKINS_HOME/jobs/*/config.xml for patterns like <password> or <credentials> that contain unencrypted plain text values. Use grep or a text search tool across all job directories.
    Affected if Any config.xml file in a job directory contains plaintext password elements that are not wrapped in <secure> tags or otherwise encrypted.
  5. Verify access control for Extended Read permission
    Review Jenkins authorization matrix or role-based access control settings to determine which users or groups have Extended Read permission on jobs. Go to Manage Jenkins > Configure Global Security > Authorization.
    Affected if Any user or group has Extended Read permission enabled, allowing them to read job configuration files.

The environment is affected if the View Cloner plugin versions 1.0 or 1.1 are installed AND any job config.xml files contain plaintext passwords accessible via Extended Read permission or filesystem access.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Identify and remove or re-encrypt stored passwords in job config.xml files affected by the view-cloner plugin, and upgrade to a patched version of the plugin once available, or remove the plugin if unused.

Recommended fix Moderate confidence

View the Jenkins plugin repository or Jenkins security advisories at www.jenkins.io for the fixed release (version after 1.1)

  1. 1. Navigate to the Jenkins dashboard
  2. 2. Go to 'Manage Jenkins' > 'Manage Plugins'
  3. 3. Click on the 'Installed' tab
  4. 4. Locate the 'view-cloner' plugin in the list
  5. 5. If an update is available, click 'Update now' to upgrade to the fixed version
  6. 6. Restart Jenkins if required to complete the installation
  7. 7. Verify the plugin has been updated to the latest version

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

Fix this in View Cloner Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing2.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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