dbcve.org
GitApplication · Jenkins

CVE-2022-36884

MEDIUM · 5.3 CVSS v3.1 Published 2022-07-27
Fix available
A fix is available. Upgrade to after 4.11.3 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
The webhook endpoint in Jenkins Git Plugin 4.11.3 and earlier provide unauthenticated attackers information about the existence of jobs configured to use an attacker-specified Git repository.

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 Git Plugin webhook endpoint in version 4.11.3 and earlier contains an information disclosure vulnerability. Unauthenticated attackers can supply a Git repository URL and receive a response indicating whether any Jenkins jobs are configured to use that specific repository, enabling reconnaissance of job configurations.

MitigationUpdate Jenkins Git Plugin to version 4.11.4 or later to patch the vulnerability. Alternatively, restrict network access to the webhook endpoint until the update can be applied.

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
GitApplication
Affected:<= 4.11.3

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Jenkins Git Plugin is installed
    Access Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Git plugin', or use the Jenkins script console: println(Jenkins.instance.pluginManager.plugins.find { it.shortName == 'git' })
    Affected if The plugin is not installed or not present in the plugin list
  2. Check the installed Git plugin version
    In Jenkins > Manage Jenkins > Manage Plugins > Installed tab, find the Git plugin and check the Version column. Compare against 4.11.3 (any version <= 4.11.3 is affected)
    Affected if The installed version is 4.11.3 or earlier (e.g., 4.11.2, 4.11.1, 4.11.0, etc.)
  3. Confirm webhook endpoint is accessible
    Check if the endpoint /git/notifyCommit is reachable on your Jenkins server. Attempt a GET request to http://your-jenkins-host/git/notifyCommit?url=test (the endpoint responds even to invalid URLs)
    Affected if The endpoint responds with any HTTP status (even error pages indicate the endpoint is exposed)
  4. Verify anonymous access is permitted
    Check Jenkins > Manage Jenkins > Configure Global Security > Authorization section. Confirm that 'Anyone can do anything' or anonymous access is enabled, or that the anonymous user has read or greater permissions
    Affected if Anonymous (unauthenticated) users can access Jenkins or the Git webhook endpoint without authentication

You are affected if the Jenkins Git Plugin is installed with version 4.11.3 or earlier AND the /git/notifyCommit webhook endpoint is accessible to unauthenticated users.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 4.11.3
Interim mitigation

Update Jenkins Git Plugin to version 4.11.4 or later to patch the vulnerability. Alternatively, restrict network access to the webhook endpoint until the update can be applied.

Recommended fix Moderate confidence

Jenkins Git Plugin version > 4.11.3 (check Jenkins plugin repository for specific fixed release)

  1. Check current Jenkins Git Plugin version in Jenkins Manage Plugins
  2. Navigate to Manage Jenkins > Manage Plugins > Installed tab
  3. Locate Git Plugin and verify version is above 4.11.3
  4. If running 4.11.3 or earlier, navigate to the Available tab or upload the newer version
  5. Restart Jenkins if required after upgrade
  6. Verify the webhook endpoint no longer returns job existence information without authentication

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Git Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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