GitHubApplication · Jenkins
CVE-2022-36885
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 · uneditedJenkins GitHub Plugin 1.34.4 and earlier uses a non-constant time comparison function when checking whether the provided and computed webhook signatures are equal, allowing attackers to use statistical methods to obtain a valid webhook signature.
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 confidenceThe Jenkins GitHub Plugin versions 1.34.4 and earlier uses a non-constant time comparison function when validating webhook signatures. This timing discrepancy allows attackers to perform statistical timing attacks to deduce the correct signature byte-by-byte, potentially allowing them to forge valid GitHub webhooks.
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
GitHubApplication
<= 1.34.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Jenkins GitHub Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins. Look for 'GitHub' in the plugin list.Affected if The plugin is not installed or has been removed entirely.
-
Determine the installed plugin versionIn the Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab and locate the GitHub Plugin. The version is displayed in the 'Version' column. Alternatively, check the plugin's manifest file (META-INF/MANIFEST.MF) within the plugin's .hpi file in $JENKINS_HOME/plugins/github/.Affected if The installed version is 1.34.4 or earlier.
-
Verify webhook configuration existsNavigate to Manage Jenkins > Configure System > GitHub > GitHub Servers. Check if any GitHub repositories or organizations are configured with webhook endpoints. Also inspect $JENKINS_HOME/github-plugin-configuration.xml if it exists.Affected if Webhook configuration exists and the plugin is configured to receive GitHub webhooks.
-
Confirm webhook endpoint is reachableCheck if the Jenkins instance exposes its webhook receiver endpoint (typically at /github-webhook/). Review network exposure using the Jenkins CLI: java -jar jenkins-cli.jar get-credential-configurations or inspect reverse proxy logs.Affected if The webhook endpoint is accessible from external networks (not firewalled or VPN-restricted).
You are affected if the Jenkins GitHub Plugin version 1.34.4 or earlier is installed AND the plugin is configured to receive GitHub webhooks, making the timing attack on webhook signature validation possible.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade the Jenkins GitHub Plugin to version 1.34.5 or later, which implements constant-time signature comparison. If immediate upgrade is not possible, monitor webhook logs for unusual timing patterns and consider additional network-level access controls.
Fix this in GitHub
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36885 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-36885 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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