Crittercism DsymApplication · Jenkins
CVE-2019-10295
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 crittercism-dsym 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 crittercism-dsym Plugin stores credentials in plain text within job config.xml files on the Jenkins master. These unencrypted credentials can be extracted by any user with Extended Read permission on jobs or by anyone with filesystem access to the Jenkins controller.
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
Crittercism DsymApplication
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.
-
Check if crittercism-dsym plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'crittercism-dsym' or 'Crittercism Dsym'. Alternatively, check the plugin directory at $JENKINS_HOME/plugins for the crittercism-dsym folder.Affected if The plugin is present in the Jenkins environment
-
Identify jobs using the crittercism-dsym pluginSearch job config.xml files for references to 'crittercism-dsym' or 'CrittercismDsym'. In the Jenkins controller filesystem, check $JENKINS_HOME/jobs/*/config.xml for these strings.Affected if Any job config.xml file contains crittercism-dsym configuration elements
-
Inspect job config.xml files for stored credentialsExamine the contents of job config.xml files that reference crittercism-dsym. Look for plain text username, password, apiKey, token, or credential fields within the crittercism-dsym configuration section.Affected if Credentials appear in plain text within the crittercism-dsym configuration section of any job config.xml
-
Check filesystem permissions on job config.xml filesReview file permissions on $JENKINS_HOME/jobs/*/config.xml files to determine which users or processes have read access to these files.Affected if Users other than administrators have filesystem read access to job config.xml files containing crittercism-dsym credentials
-
Verify who has Extended Read permission on jobsReview Jenkins matrix-based security or folder-based permission settings to identify users or groups granted Extended Read permission on jobs that use the crittercism-dsym plugin.Affected if Any user or group has Extended Read permission on jobs configured with crittercism-dsym
A user is affected if the crittercism-dsym plugin is installed and any job's config.xml file contains plain text credentials for this plugin, especially when users with Extended Read permission or filesystem access exist beyond trusted administrators.
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 dataIdentify all jobs using the plugin and remove stored credentials from their configurations. Rotate any exposed credentials immediately. Consider upgrading to a patched plugin version if available.
Fix this in Crittercism Dsym
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10295 — 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-10295 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