Data Theorem Mobile App SecurityApplication · Jenkins
CVE-2019-10413
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 Data Theorem: CI/CD Plugin 1.3 and earlier stored credentials unencrypted in job config.xml files on the Jenkins master where they could 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 Data Theorem CI/CD Plugin versions 1.3 and earlier stores credentials in plain text within job config.xml files on the Jenkins master. This exposes credentials to any user with Extended Read permission in Jenkins or anyone with filesystem access to the master.
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
Data Theorem Mobile App SecurityApplication
<= 1.3CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check if Data Theorem CI/CD Plugin is installedGo to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Data Theorem' or 'Mobile App Security' in the plugin listAffected if Plugin is listed as installed with version 1.3 or earlier
-
Verify the plugin versionIn the Installed Plugins tab, locate the Data Theorem Mobile App Security plugin and note the Version column valueAffected if Version is 1.3 or earlier
-
Identify jobs using the pluginReview Jenkins jobs that use Data Theorem CI/CD integration - look for jobs with Data Theorem build steps configured in job configurationAffected if Jobs exist that utilize Data Theorem plugin features and store credentials
-
Inspect job config.xml for plain text credentialsNavigate to JENKINS_HOME/jobs/JOBNAME/config.xml for each job using the plugin; open the XML file and search for credential fields (passwords, API keys, tokens) - they will appear as plain readable text rather than encryptedAffected if Plain text credentials (not <encrypted> or masked) are found in the config.xml files
-
Check Extended Read permission assignmentsGo to Jenkins > Manage Jenkins > Manage and Assign Users > Assign Roles (if using Matrix Authorization) or check user/group permissions; look for Extended Read permission granted broadlyAffected if Extended Read permission is granted to users or groups beyond trusted administrators
You are affected if the Data Theorem CI/CD Plugin version 1.3 or earlier is installed AND jobs using the plugin exist with credentials stored in config.xml files, especially if Extended Read permission is widely granted.
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 Data Theorem CI/CD Plugin to version 1.4 or later, which encrypts credentials. Review and rotate any credentials that may have been exposed, and restrict Extended Read permission to only trusted users.
Fix this in Data Theorem Mobile App Security
Scoped from the published advisory
- Consultation4.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10413 — 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-10413 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