CVE-2018-1000110: Incorrect Authorization in Jenkins Git Plugin

org.jenkins-ci.plugins:git Updated 02 Oct 2025

Summary

13/05/2022
Yes i
Moderate
5.3

CVE-2018-1000110: Incorrect Authorization in Jenkins Git Plugin. Affects org.jenkins-ci.plugins:git versions < 3.8.0. Fixed in 3.8.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Jenkins Git Plugin is a popular open-source plugin for the Jenkins automation server that allows users to integrate Git repositories into their Jenkins projects. It provides functionality for cloning, fetching, and pushing to Git repositories. The plugin is widely used in software development and continuous integration workflows.

Vulnerability Detail

The Jenkins Git Plugin version 3.7.0 and earlier are affected by an improper authorization vulnerability. The vulnerability resides in the GitStatus.java file and allows an attacker with network access to obtain a list of nodes and users. This unauthorized access can lead to information disclosure and potential misuse of sensitive data. The vulnerability has a CVSS score of 5.3, indicating a moderate severity level.

How To Fix

Minimum fixed version

3.8.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, users can restrict network access to the Jenkins server to trusted sources only. This can be achieved by configuring firewall rules or network access control lists (ACLs) to limit incoming connections to the Jenkins server. By doing so, the risk of unauthorized access and information disclosure can be mitigated.

Conclusion

The Jenkins Git Plugin version 3.7.0 and earlier are affected by an improper authorization vulnerability that allows unauthorized access to a list of nodes and users. To mitigate this vulnerability, it is recommended to upgrade to version 3.8.0 or later. Alternatively, users can restrict network access to the Jenkins server as a temporary workaround. For further assistance or support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.jenkins-ci.plugins:git →

Share this vulnerability

FAQ

The vulnerability allows an attacker with network access to obtain a list of nodes and users in the Jenkins Git Plugin. This can lead to information disclosure and potential misuse of sensitive data.

There is no known exploit available for this vulnerability at the moment. However, it is important to apply the recommended fix or workaround to prevent any potential exploitation.

No, only versions 3.7.0 and earlier are affected by this vulnerability. Users of later versions are not impacted and do not need to take any action.

Yes, the vulnerability can be exploited remotely by an attacker with network access to the Jenkins server. It is important to apply the necessary fixes or workarounds to mitigate the risk.

At the moment, there are no alternative plugins or solutions available for this specific functionality provided by the Jenkins Git Plugin. It is recommended to update to the fixed version or apply the suggested workaround.

Related vulnerabilities

Recent vulnerabilities recorded for org.jenkins-ci.plugins:git.

How To Fix

Minimum fixed version

3.8.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback