Crowd2Application · Atlassian
CVE-2018-1000423
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 · uneditedAn insufficiently protected credentials vulnerability exists in Jenkins Crowd 2 Integration Plugin 2.0.0 and earlier in CrowdSecurityRealm.java, CrowdConfigurationService.java that allows attackers with local file system access to obtain the credentials used to connect to Crowd 2.
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 2 Integration Plugin versions 2.0.0 and earlier stores authentication credentials (Crowd username/password) in plaintext within configuration files (CrowdSecurityRealm.java, CrowdConfigurationService.java). Attackers with local file system access to the Jenkins controller can read these files to obtain the cleartext credentials used to connect to the Crowd 2 server.
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
Crowd2Application
<= 2.0.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/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 Crowd 2 Integration Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed and look for 'Crowd 2 Integration' in the list, or check the $JENKINS_HOME/plugins directory for crowd2 plugin folderAffected if The Crowd 2 Integration Plugin is present in the Jenkins installation
-
Check the installed plugin versionIn Manage Jenkins > Manage Plugins > Installed, find Crowd 2 Integration and note the version number displayedAffected if The plugin version is 2.0.0 or earlier (any version up to and including 2.0.0)
-
Determine if Crowd authentication is configuredNavigate to Manage Jenkins > Configure Global Security > Security Realm and check if 'Crowd 2 Security Realm' or similar Crowd-based authentication is selectedAffected if Crowd authentication is enabled as the security realm in Jenkins global security settings
-
Locate Crowd plugin configuration filesSearch in $JENKINS_HOME for files named 'CrowdSecurityRealm' or 'CrowdConfigurationService' (may have .xml, .xml.bak, or other extensions), typically found under $JENKINS_HOME/init.groovy.d/ or within plugin configuration directoriesAffected if Configuration files related to Crowd security realm exist on the Jenkins controller file system
A user is affected if the Crowd 2 Integration Plugin version 2.0.0 or earlier is installed AND Crowd authentication is configured as the security realm, with configuration files potentially containing plaintext credentials accessible on the local file system.
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 dataUpdate the Crowd 2 Integration Plugin to a version that addresses insufficient credential protection. Immediately rotate all exposed Crowd credentials. Restrict file system permissions on Jenkins configuration directories to prevent unauthorized local access.
Fix this in Crowd2
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000423 — 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-2018-1000423 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