dbcve.org
Gitlab HookApplication · Jenkins

CVE-2018-1000196

MEDIUM · 6.5 CVSS v3.0 Published 2018-06-05
Fix available
A fix is available. Upgrade to after 1.4.2 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
A exposure of sensitive information vulnerability exists in Jenkins Gitlab Hook Plugin 1.4.2 and older in gitlab_notifier.rb, views/gitlab_notifier/global.erb that allows attackers with local Jenkins master file system access or control of a Jenkins administrator's web browser (e.g. malicious extension) to retrieve the configured Gitlab token.

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 Gitlab Hook Plugin versions 1.4.2 and older exposes the configured Gitlab API token in the global.erb view file (gitlab_notifier.rb). An attacker with local file system access to the Jenkins master or who controls the Jenkins administrator's web browser (e.g., via a malicious browser extension) can retrieve the sensitive Gitlab token.

MitigationUpgrade the Jenkins Gitlab Hook Plugin to a version newer than 1.4.2 that removes the token exposure from the view, and audit browser extensions with access to Jenkins admin pages.

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
Gitlab HookApplication
Affected:<= 1.4.2

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

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

  1. Verify Gitlab Hook Plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Gitlab Hook' or 'gitlab-hook' to confirm the plugin is present.
    Affected if The plugin is installed and appears in the list of installed plugins.
  2. Check the installed plugin version
    In the Installed Plugins tab, locate the Gitlab Hook Plugin and note the version number displayed in the 'Version' column.
    Affected if The version is 1.4.2 or any version lower than 1.4.2.
  3. Locate the vulnerable view file
    On the Jenkins master file system, find the plugin's view file named global.erb (referenced as gitlab_notifier.rb in the plugin's views directory). This is typically under $JENKINS_HOME/plugins/gitlab-hook/WEB-INF/views/ or similar.
    Affected if The file global.erb exists in the plugin directory structure.
  4. Inspect the view file for exposed token
    Open the global.erb file in a text editor and search for patterns resembling API tokens (long alphanumeric strings, particularly in gitlabToken or similar configuration fields).
    Affected if The file contains a visible Gitlab API token value in plain text or as a filled form field value.
  5. Check if Gitlab API token is configured
    Navigate to Jenkins > Manage Jenkins > Configure System > Gitlab Hook section (or similar configuration page) and check if a Gitlab API Token field contains a visible/accessible token value.
    Affected if A Gitlab API Token has been configured and is visible or accessible through the web interface.

A user is affected if the Gitlab Hook Plugin version is 1.4.2 or older AND a Gitlab API token has been configured, as the token would be exposed in the global.erb view file.

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.4.2
Interim mitigation

Upgrade the Jenkins Gitlab Hook Plugin to a version newer than 1.4.2 that removes the token exposure from the view, and audit browser extensions with access to Jenkins admin pages.

Fix this in Gitlab Hook Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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