Extensive TestingApplication · Jenkins
CVE-2019-10448
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 · uneditedJenkins Extensive Testing 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 confidenceThe Jenkins Extensive Testing Plugin stores credentials in plaintext (unencrypted) within job config.xml files on the Jenkins master. These config files are accessible to users with Extended Read permission on Jenkins jobs, or to anyone with direct file system access to the Jenkins master server, exposing stored credentials.
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
Extensive TestingApplication
= 1.4.3= 1.4.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Extensive Testing plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed, search for 'Extensive Testing' or 'extensivetesting', or list files in $JENKINS_HOME/plugins/ directoryAffected if The plugin is present and its version is 1.4.3 or 1.4.4
-
Identify jobs using the pluginSearch for jobs containing 'extensivetesting' in their config.xml files located in $JENKINS_HOME/jobs/<jobname>/config.xml, or inspect job configuration pages for Extensive Testing plugin sectionsAffected if Jobs are configured to use the Extensive Testing plugin with credential fields populated
-
Inspect job config.xml for plaintext credentialsOpen the config.xml file for a job using the Extensive Testing plugin and search for credential-related XML elements (such as <credentialsId>, <username>, <password>, or similar fields) to see if values appear as plaintext rather than encrypted <secret> entriesAffected if Credentials in the config.xml are stored in plaintext (readable text) rather than encrypted form
-
Check Extended Read permission exposureReview user permissions in Jenkins under Manage Jenkins > Manage Users and in job-level configuration; verify if any users or groups have Extended Read permission enabled, which allows reading config.xml content without full administrative accessAffected if Extended Read permission is granted to any user group or individual beyond administrators
A user is affected if the Extensive Testing plugin versions 1.4.3 or 1.4.4 are installed, jobs are configured with credentials using this plugin, and those credentials appear as plaintext in config.xml files or are accessible via Extended Read permission.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade the Extensive Testing Plugin to a patched version that encrypts credentials at rest, or migrate credentials to Jenkins' built-in credential storage mechanism; restrict Extended Read permission and limit file system access to the Jenkins master.
Fix this in Extensive Testing
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10448 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10448 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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