dbcve.org
Testquality UpdaterApplication · Jenkins

CVE-2023-24454

MEDIUM · 5.5 CVSS v3.1 Published 2023-01-26
Fix available
A fix is available. Upgrade to after 1.3 or later.
See remediation →
57/100
Remediation priority · Elevated
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 TestQuality Updater Plugin 1.3 and earlier stores the TestQuality Updater password unencrypted in its global configuration file on the Jenkins controller where it can be viewed by users with 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 Jenkins TestQuality Updater Plugin versions 1.3 and earlier stores the TestQuality Updater password in plaintext within its global configuration file on the Jenkins controller. Users with file system access to the Jenkins controller can read this configuration file and obtain the password in unencrypted form.

MitigationUpgrade to a patched version of the TestQuality Updater Plugin that encrypts stored passwords, or if no patch exists, manually rotate the exposed password and implement alternative secure credential storage mechanisms.

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
Testquality UpdaterApplication
Affected:<= 1.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/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. Verify TestQuality Updater plugin installation and version
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins TestQuality-Updater. Check if the plugin is listed and note its version.
    Affected if The plugin version is 1.3 or earlier, or the version cannot be determined (plugin is installed but version info is unavailable).
  2. Locate the TestQuality Updater global configuration file
    Navigate to the Jenkins home directory and find the configuration file, typically located at JENKINS_HOME/org.jenkinsci.plugins.testqualityupdater.TestQualityUpdater.xml or within the Jenkins internal configuration structure.
    Affected if The configuration file exists in the Jenkins home directory.
  3. Inspect configuration for plaintext password
    Open the configuration file with a text editor or use: cat JENKINS_HOME/org.jenkinsci.plugins.testqualityupdater.TestQualityUpdater.xml. Look for plaintext password strings in the <password> or similar XML elements.
    Affected if The password field contains an unencrypted, plaintext value rather than an encrypted or masked value.
  4. Confirm the plugin has an active configuration
    Navigate to Jenkins > Manage Jenkins > Configure System and look for the TestQuality Updater section. Check if credentials are configured and saved.
    Affected if TestQuality Updater is configured with stored credentials and the configuration file contains plaintext password data.

Your environment is affected if the TestQuality Updater plugin version 1.3 or earlier is installed and its configuration file contains an unencrypted password in plaintext form.

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 1.3
Interim mitigation

Upgrade to a patched version of the TestQuality Updater Plugin that encrypts stored passwords, or if no patch exists, manually rotate the exposed password and implement alternative secure credential storage mechanisms.

Fix this in Testquality Updater Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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