IcescrumApplication · Jenkins
CVE-2019-10443
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 iceScrum Plugin 1.1.4 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 iceScrum Plugin versions 1.1.4 and earlier stored user credentials in plain text (unencrypted) within job config.xml files on the Jenkins master. Users with Extended Read permission could view these credentials through the Jenkins UI, or anyone with physical or file system access to the master could read them directly from the config.xml 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
IcescrumApplication
<= 1.1.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.
-
Identify if iceScrum plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or inspect the plugins directory for icescrum.jar. Check the plugin version listed.Affected if iceScrum plugin version 1.1.4 or earlier is installed
-
Locate job config.xml files with iceScrum configurationSearch the JENKINS_HOME/jobs/*/config.xml files for the presence of <icescrum> or iceScrum-related configuration sections.Affected if config.xml files contain iceScrum configuration entries
-
Inspect credentials storage in config.xmlOpen the config.xml files that contain iceScrum configuration and search for <password>, <credentials>, or <secret> elements within the iceScrum section.Affected if Credentials are stored as plain text (unencrypted) values in the config.xml files rather than using Jenkins credential bindings or encrypted storage
-
Verify Extended Read permission exposureReview which users or groups have Extended Read permission in Jenkins > Manage Jenkins > Configure Global Security > Authorization, and identify if any non-admin users can view job configurations.Affected if Non-admin users have Extended Read permission and can therefore view plain text credentials through the UI
You are affected if iceScrum plugin version 1.1.4 or earlier is installed AND job config.xml files contain plain text credentials in iceScrum configuration sections that are readable by users with 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 iceScrum Plugin to version 1.2.0 or later which encrypts credentials. Immediately rotate any credentials that may have been exposed. As a short-term workaround, revoke Extended Read permission from non-admin users and limit filesystem access to the Jenkins master.
Fix this in Icescrum
Scoped from the published advisory
- Consultation4.0 h
- Implementation3.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10443 — 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-10443 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