dbcve.org
Jabber \(xmpp\) Notifier And ControlApplication · Jenkins

CVE-2021-21634

MEDIUM · 6.5 CVSS v3.1 Published 2021-03-30
Fix available
A fix is available. Upgrade to after 1.41 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Jenkins Jabber (XMPP) notifier and control Plugin 1.41 and earlier stores passwords unencrypted in its global configuration file on the Jenkins controller where they can be viewed by users with access to the Jenkins controller 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 confidence

The Jenkins Jabber (XMPP) notifier and control Plugin versions 1.41 and earlier stores passwords in plaintext/unencrypted in its global configuration file on the Jenkins controller filesystem. Users with access to the Jenkins controller file system can view these stored credentials.

MitigationUpdate the Jenkins Jabber plugin to a version that encrypts stored passwords (if available), and rotate any credentials that may have been exposed via plaintext storage.

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 \(xmpp\) Notifier And ControlApplication
Affected:<= 1.41

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Jabber plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or check the version file in $JENKINS_HOME/plugins/jabber/WEB-INF/detached-plugins/ (or via jenkins-cli.jar or REST API)
    Affected if Version is 1.41 or lower (the plugin version is displayed in the plugin manager)
  2. Locate the Jabber plugin global configuration file
    Navigate to the Jenkins home directory and find the Jabber plugin configuration, typically stored in $JENKINS_HOME/hudson.plugins.jabber.JabberPlugin.xml or similar path under $JENKINS_HOME/
    Affected if Configuration file exists in the Jenkins home directory (the plugin has been configured)
  3. Inspect configuration file for plaintext credentials
    Open the configuration XML file with a text editor or use 'cat' to view its contents, looking for password fields in the XML
    Affected if Password values appear in plaintext (unencrypted) within the XML elements rather than being stored in the encrypted form (Jenkins uses FormFieldAction.encryptedValue or similar encryption markers)
  4. Check file permissions on configuration
    Use 'ls -la' on the configuration file to verify who has read access to the file containing the credentials
    Affected if The configuration file is readable by users other than the Jenkins service account (world-readable or group-readable)
  5. Verify if target XMPP/Jabber settings are configured
    Review the configuration file contents to confirm if Jabber/XMPP server, credentials, or notification settings have been configured and saved
    Affected if The plugin has been configured with actual Jabber credentials (not just installed but never configured)
  6. Cross-reference with Jenkins credentials store
    Check if the plugin is using Jenkins credentials store (Manage Jenkins > Manage Credentials) or storing passwords directly in the plugin config XML
    Affected if Passwords are stored directly in the plugin XML rather than referencing credential IDs from the Jenkins credentials store

A user is affected if the Jabber plugin version is 1.41 or earlier AND the plugin has been configured with credentials that are stored in plaintext/unencrypted form in the configuration XML file accessible via the filesystem.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.41
Interim mitigation

Update the Jenkins Jabber plugin to a version that encrypts stored passwords (if available), and rotate any credentials that may have been exposed via plaintext storage.

Fix this in Jabber \(xmpp\) Notifier And Control Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-21634 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-21634 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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