Jenkins HipChat Plugin allows credential capture due to incorrect authorization

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.8 · CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2018-1000418: 1.06% estimated exploitation activity in the next 30 days; percentile 64.72 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

An improper authorization vulnerability exists in Jenkins HipChat Plugin 2.2.0 and earlier in HipChatNotifier.java that allows attackers with Overall/Read access to send test notifications to an attacker-specified HipChat server with attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins. As of version 2.2.1, this form validation method requires POST requests and Overall/Administer permissions.

Published by the source

13 May 2022, 01:18 UTC

Last modified by the source

2 Feb 2023, 05:01 UTC

Source last checked

26 Oct 2026, 16:07 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-w3f7-2qfw-348x

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2018-1000418

Advisory: Jenkins HipChat Plugin allows credential capture due to incorrect authorization
IDs: CVE-2018-1000418, GHSA-w3f7-2qfw-348x
Record: https://patchnext.com/advisories/cve-2018-1000418 (revision 1, source checked 26 Oct 2026, 16:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.jvnet.hudson.plugins:hipchat 2.2.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.jvnet.hudson.plugins:hipchat: affected < 2.2.1; fixed in 2.2.1

## Suggested inspection (read-only)
- Maven org.jvnet.hudson.plugins:hipchat: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.jvnet.hudson.plugins:hipchat.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-w3f7-2qfw-348x (GitHub-reviewed advisory GHSA-w3f7-2qfw-348x lists affected ranges: Maven org.jvnet.hudson.plugins:hipchat >=0 <2.2.1)

Commands are suggestions: review each one before running it.