🛡️ CVE-2018-1000196 — gitlab-hook
Description
Jenkins Gitlab Hook Plugin stores and displays GitLab API token in plain text
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.
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity none, availability none.
Weakness class
CVE-2018-1000196 is classified as CWE-200: Exposure of Sensitive Information. Information that should stay internal is disclosed to someone who is not authorised to see it.
Affected software
CVE-2018-1000196 is recorded against 1 package.
- org.jenkins-ci.ruby-plugins:gitlab-hook
Timeline and source
Published on 14 May 2022 and last revised on 16 February 2024. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
Details
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| org.jenkins-ci.ruby-plugins:gitlab-hook | — | — |
References
Similar Threats
- Unknown CVE-2020-2096
More CVE 2018 advisories
Browse all of CVE 2018 in the advisory index.
Free Vulnerability Check
Is your site affected by CVE-2018-1000196?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against CVE-2018-1000196 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.