Jabber ServerApplication · Jenkins
CVE-2019-10288
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 Jabber Server Plugin stores credentials unencrypted in its global 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 Jabber Server Plugin stores credentials in plaintext (unencrypted) in its global configuration file on the Jenkins master filesystem. Any user with access to the master file system can view these stored credentials, leading to credential exposure.
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
Jabber ServerApplication
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.
-
Verify Jabber Server Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Jabber' or 'Jabber Server' in the list of installed pluginsAffected if The Jabber Server Plugin appears in the installed plugins list
-
Locate the Jabber Server Plugin configuration fileNavigate to Jenkins > Manage Jenkins > Configure System and look for the 'Jabber Server' section. The configuration is typically stored in the Jenkins configuration directory (usually $JENKINS_HOME) in an XML file related to the pluginAffected if You can access the Jabber Server configuration section in Jenkins global configuration
-
Inspect configuration for stored credentialsExamine the configuration file (search for files containing 'jabber' in the Jenkins home directory) and look for credential fields - check whether username, password, or API token values appear as plaintext readable strings rather than being masked or stored as credential ID referencesAffected if Username, password, or token values are visible as plaintext strings in the configuration
-
Verify filesystem access to configurationCheck file system permissions on the Jenkins configuration directory and the jabber plugin configuration file - use 'ls -la' or equivalent to list owner and permissionsAffected if The configuration file is readable by users other than the Jenkins service account (world-readable or group-readable with accessible groups)
If the Jabber Server Plugin is installed and plaintext credentials are present in its configuration file that is accessible to unauthorized users, 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 dataMigrate stored credentials to Jenkins' built-in credential storage mechanism (Credentials Plugin), rotate all exposed credentials immediately, and restrict filesystem access to the Jenkins master configuration directory.
Fix this in Jabber Server
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-10288 — 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-10288 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