dbcve.org
Instant MessagingApplication · Jenkins

CVE-2022-28135

MEDIUM · 6.5 CVSS v3.1 Published 2022-03-29
Fix available
A fix is available. Upgrade to 1.42 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 instant-messaging Plugin 1.41 and earlier stores passwords for group chats unencrypted in the global configuration file of plugins based on Jenkins instant-messaging Plugin 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

Jenkins instant-messaging Plugin versions 1.41 and earlier stores group chat passwords in plaintext within its global configuration file on the Jenkins controller file system. Users with access to the Jenkins controller's file system can view these unencrypted passwords.

MitigationUpgrade Jenkins instant-messaging Plugin to version 1.42 or later. Additionally, rotate any exposed group chat passwords as a precautionary measure since they may have been compromised.

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
Instant MessagingApplication
Affected:< 1.42

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. Verify instant-messaging plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Instant Messaging', or inspect the $JENKINS_HOME/plugins directory for a folder named 'instant-messaging' or similar.
    Affected if The plugin is present in the Jenkins environment
  2. Determine installed plugin version
    In the Manage Plugins > Installed section, locate the Instant Messaging plugin and note the version number displayed. Alternatively, check the version file within the plugin's directory (e.g., $JENKINS_HOME/plugins/instant-messaging/META-INF/MANIFEST.MF).
    Affected if The installed version is 1.41 or earlier (versions below 1.42)
  3. Locate the plugin's global configuration file
    The instant-messaging plugin typically stores its configuration in the Jenkins global configuration directory. Check $JENKINS_HOME/org.jenkinsci.plugins.instantmessaging.config.xml or look for XML files containing 'instantmessaging' or 'instant-messaging' in the $JENKINS_HOME directory.
    Affected if A configuration file for the instant-messaging plugin exists on the Jenkins controller file system
  4. Inspect configuration for plaintext passwords
    Open the identified configuration file and search for password-related XML elements (e.g., <password>, <groupChatPassword>, or similar). Visually inspect whether any password values appear in plaintext rather than being encrypted or masked.
    Affected if The configuration file contains visible plaintext passwords in password-related fields

The environment is affected if the instant-messaging plugin version 1.41 or earlier is installed AND a global configuration file exists containing plaintext group chat passwords.

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.

dbcve · scoped
Upgrade available Upgrade to 1.42 or later
Fixed in 1.42
Interim mitigation

Upgrade Jenkins instant-messaging Plugin to version 1.42 or later. Additionally, rotate any exposed group chat passwords as a precautionary measure since they may have been compromised.

Recommended fix High confidence

version 1.42 or later

  1. Check the currently installed version of the Jenkins instant-messaging plugin in Manage Jenkins > Manage Plugins
  2. Backup your Jenkins configuration and any custom configurations for the instant-messaging plugin
  3. Navigate to Manage Jenkins > Manage Plugins > Updates tab
  4. Find the instant-messaging plugin in the list and select it for update
  5. Click 'Download now and install after restart' to upgrade to the latest version
  6. After Jenkins restarts, verify the plugin was upgraded to version 1.42 or later in the Installed tab
  7. If you have existing group chat configurations, review them to ensure credentials are properly managed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Instant Messaging Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-28135 — 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-2022-28135 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