HipchatApplication · Atlassian
CVE-2018-1000419
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 improper authorization vulnerability exists in Jenkins HipChat Plugin 2.2.0 and earlier in HipChatNotifier.java that allows attackers with Overall/Read access to obtain credentials IDs for credentials stored in Jenkins.
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 HipChat plugin for Jenkins contains an improper authorization vulnerability in HipChatNotifier.java where the plugin fails to properly restrict access to credential information. Users with only Overall/Read permission (read-only access) can enumerate and obtain credential IDs stored in Jenkins, exposing identifiers that should be protected from unauthorized disclosure.
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
HipchatApplication
<= 2.2.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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify HipChat plugin installationIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'HipChat' or check the plugins directory for the HipChat plugin fileAffected if HipChat plugin is present in Jenkins
-
Check HipChat plugin versionIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab, find the HipChat plugin, and note the version number displayedAffected if Version is 2.2.0 or earlier (any version <= 2.2.0)
-
Verify users with Overall/Read permissionIn Jenkins, go to Manage Jenkins > Manage Users or check Configure Global Security to review users and groups that have Overall/Read permission assignedAffected if Any user or group has Overall/Read permission enabled in Jenkins
-
Confirm credential storage existsIn Jenkins, go to Credentials > System > Global credentials (or check if any credentials are stored in Jenkins credential stores)Affected if Any credentials are stored in Jenkins (the vulnerability exposes credential IDs stored in the system)
A user is affected if the HipChat plugin version is 2.2.0 or earlier AND any user has Overall/Read permission AND credentials are stored in Jenkins, as this combination allows unauthorized credential ID enumeration.
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 Jenkins HipChat Plugin to version 2.2.1 or later. If immediate patching is not feasible, audit all users with Overall/Read access and restrict this permission to only trusted personnel, as they can now enumerate credential IDs.
Fix this in Hipchat
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000419 — 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-1000419 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