Diawi UploadApplication · Jenkins
CVE-2019-10284
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 Diawi Upload 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 Diawi Upload Plugin stores credentials in plain text within job config.xml files on the Jenkins master. Users with Extended Read permission or filesystem access to the master can view these unencrypted credentials, leading to credential exposure.
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
Diawi UploadApplication
all versionsCVSS 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 Diawi Upload plugin is installedIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed and look for 'Diawi Upload' in the list. Alternatively, check the plugins directory on the Jenkins master for a diawi-upload folder.Affected if The Diawi Upload plugin appears in the installed plugins list
-
Locate job config.xml files containing Diawi Upload configurationNavigate to the Jenkins jobs directory on the master (typically $JENKINS_HOME/jobs/<jobname>/config.xml) and search for 'diawi' or 'DiawiUpload' within config.xml files.Affected if Any config.xml file contains Diawi Upload plugin configuration entries
-
Inspect for plain text credentials in job configurationOpen the config.xml files identified in the previous step and look for credential fields (apiToken, password, or similar credential-related parameters) that store values in plain text rather than referencing Jenkins credential IDs.Affected if Credential values appear as readable text strings rather than as <credentialsId> references to the Jenkins Credentials Plugin
-
Verify if Extended Read permission is granted to usersCheck Jenkins authorization matrix or matrix-based security settings at Manage Jenkins > Configure Global Security to see which users or groups have Extended Read permission.Affected if Any user or group other than administrators has Extended Read permission enabled
If the Diawi Upload plugin is installed and its job config.xml files contain plain text credential values accessible to users with Extended Read permission, the environment is affected by this CVE.
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 dataMigrate credentials from the plugin's storage to Jenkins' built-in Credentials Plugin (which encrypts credentials), then update job configurations to reference the stored credentials. Consider replacing the plugin with a secured alternative if it cannot properly use the credential store.
Fix this in Diawi Upload
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing2.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,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10284 — 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-10284 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