Crowd IntegrationApplication · Jenkins
CVE-2019-1003097
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 Crowd Integration Plugin stores credentials unencrypted in the global config.xml configuration file on the Jenkins master where they can be viewed by users with 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 Crowd Integration Plugin stores user credentials in plaintext within the global config.xml file on the Jenkins master. Anyone with file system access to the Jenkins master can read these unencrypted credentials directly from the configuration file.
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
Crowd IntegrationApplication
<= 1.2CVSS 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.
-
Verify Crowd Integration Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed, or use the Jenkins CLI: java -jar jenkins-cli.jar -s http://localhost:8080/ list-plugins | grep -i crowdAffected if The Crowd Integration Plugin appears in the installed plugins list
-
Check installed plugin versionIn the Installed Plugins page, find the Crowd Integration Plugin version. Alternatively, inspect the plugin's .jpi file in $JENKINS_HOME/plugins/ for the manifest. Compare the version number to the affected range (1.2 and below)Affected if The installed version is 1.2 or lower
-
Confirm plugin configuration existsInspect the global configuration file at $JENKINS_HOME/config.xml for crowd-related settings, or navigate to Manage Jenkins > Configure System and look for Crowd/Atlassian Crowd settingsAffected if The Crowd Integration Plugin has been configured with at least one application and credentials
-
Inspect credentials storage for plaintextExamine the $JENKINS_HOME/config.xml file directly for plaintext password elements within the <com.denimgroup.jenkins.crowd> or similar crowd plugin configuration sectionAffected if The config.xml contains unencrypted (plaintext) password strings in the crowd plugin configuration section
If the Crowd Integration Plugin version 1.2 or lower is installed AND configured, and config.xml contains plaintext passwords in the crowd configuration section, 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 dataRestrict file system access to the Jenkins master and config.xml. Update to a patched version of the Crowd Integration Plugin that encrypts credentials or leverages Jenkins' built-in credentials storage mechanism.
Fix this in Crowd Integration
Scoped from the published advisory
- Consultation3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1003097 — 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-1003097 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