MablApplication · Jenkins
CVE-2019-10283
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 mabl 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 mabl Plugin stores credentials in plaintext within job config.xml files on the Jenkins master. Users with Extended Read permission or filesystem-level access to the master can view these unencrypted credentials directly from the configuration files.
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
MablApplication
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.
-
Identify if mabl plugin is installedCheck the Jenkins plugin directory (typically $JENKINS_HOME/plugins/) for the mabl plugin folder, or use the Jenkins CLI: java -jar jenkins-cli.jar -s http://[jenkins] list-plugins 2>/dev/null | grep -i mablAffected if The mabl plugin appears in the installed plugins list
-
Locate job config.xml files using mablSearch for config.xml files in $JENKINS_HOME/jobs/*/ that contain 'mabl' as a keyword, for example: grep -rl 'mabl' $JENKINS_HOME/jobs/*/config.xml 2>/dev/nullAffected if Any config.xml files are found containing mabl configuration entries
-
Inspect job config.xml for plaintext credentialsExamine the contents of each config.xml file identified in the previous step, specifically looking for credential-related fields within the mabl plugin configuration section. Example: cat $JENKINS_HOME/jobs/[jobname]/config.xml | grep -A20 'mabl'Affected if Credentials (such as API keys, tokens, or secret values) appear in plaintext within the mabl plugin section of any config.xml file
-
Verify filesystem access to config.xml filesCheck file permissions on the identified config.xml files: ls -la $JENKINS_HOME/jobs/*/config.xmlAffected if Files are readable by users other than the Jenkins service account (world-readable or readable by other non-admin users)
If the mabl plugin is installed and any job's config.xml file contains unencrypted credential values within the mabl configuration section, the environment is affected by this vulnerability.
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 to a patched version of the mabl Plugin and rotate all credentials that may have been exposed; consider reviewing user permissions and access controls.
Fix this in Mabl
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10283 — 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-10283 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