dbcve.org
Klaros TestmanagementApplication · Jenkins

CVE-2019-10282

HIGH · 8.8 CVSS v3.1 Published 2019-04-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 Klaros-Testmanagement Plugin stores credentials unencrypted in job config.xml files on the Jenkins master where they can be viewed by users with Extended Read permission, or access to the master 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 Klaros-Testmanagement Plugin for Jenkins stores credentials (likely API tokens or passwords) in plain text within job config.xml files. These config files are accessible to users with Extended Read permission on Jenkins, which is intended to be a limited permission, and to anyone with filesystem access to the Jenkins master.

MitigationImmediately rotate any credentials that may have been stored by this plugin, as they are compromised. Upgrade to a patched version of the plugin that handles credentials properly, and review job configurations to ensure no plain-text credentials remain.

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
Klaros TestmanagementApplication
Affected:all versions

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Confirm Klaros-Testmanagement plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed, or use the Jenkins CLI: java -jar jenkins-cli.jar -s http://localhost:8080 list-plugins
    Affected if The Klaros-Testmanagement plugin appears in the installed plugins list
  2. Locate job config.xml files that use the plugin
    Search the Jenkins jobs directory (typically $JENKINS_HOME/jobs/*/config.xml) for occurrences of 'klaros' in the file contents, or inspect individual job configurations through the UI at /job/JOBNAME/configure
    Affected if Job config.xml files contain <klaros> or related XML elements storing credentials in plain text
  3. Inspect credential storage format in config.xml
    Open affected config.xml files and examine the <klaros> section for plain-text username/password or API token fields rather than encrypted credential IDs
    Affected if Credentials appear as readable text values rather than <credentialsId> references to the Jenkins credential store
  4. Verify Extended Read permission assignments
    Check Jenkins authorization matrix at Manage Jenkins > Configure Global Security, or review matrix-authorization-strategy entries in configuration files
    Affected if Users or groups are granted Extended Read permission, allowing them to read job config.xml files
  5. Check filesystem access to Jenkins master
    Review file system permissions on $JENKINS_HOME/jobs/ directory and ensure untrusted users do not have read access to config.xml files
    Affected if Any user account other than the Jenkins service account can read the jobs directory containing config.xml files

If the Klaros-Testmanagement plugin is installed and its job config.xml files contain plain-text credentials accessible via Extended Read or filesystem access, the environment is affected by this CVE.

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

Immediately rotate any credentials that may have been stored by this plugin, as they are compromised. Upgrade to a patched version of the plugin that handles credentials properly, and review job configurations to ensure no plain-text credentials remain.

Fix this in Klaros Testmanagement Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing2.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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