Generic Webhook TriggerApplication · Jenkins

CVE-2022-43412

MEDIUM · 5.3 CVSS v3.1 Published 2022-10-19

Fix available

A fix is available. Upgrade to 1.84.2 or later.

See remediation →

62/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Jenkins Generic Webhook Trigger Plugin 1.84.1 and earlier uses a non-constant time comparison function when checking whether the provided and expected webhook token are equal, potentially allowing attackers to use statistical methods to obtain a valid webhook token.

Technical summary

dbcve analysis · high confidence

The Jenkins Generic Webhook Trigger Plugin versions 1.84.1 and earlier uses a non-constant time comparison function when validating webhook tokens, enabling timing attacks that could allow attackers to deduce valid tokens through statistical analysis of response times.

MitigationUpgrade to Jenkins Generic Webhook Trigger Plugin version 1.84.2 or later which implements constant-time comparison for token validation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Generic Webhook TriggerApplication

Affected:< 1.84.2

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Verify the Generic Webhook Trigger Plugin is installed

Access the Jenkins script console at /script or navigate to Manage Jenkins > Manage Plugins > Installed and search for 'Generic Webhook Trigger'

Affected if The plugin appears in the installed plugins list
Determine the installed version of the plugin

In the Installed Plugins page, locate the Generic Webhook Trigger plugin and note the version number displayed in the 'Version' column

Affected if The version listed is 1.84.1 or earlier
Confirm webhook tokens are configured

Navigate to a job configured with Generic Webhook Trigger, or check the plugin configuration at Manage Jenkins > Configure System > Generic Webhook Trigger Plugin, and look for any token fields or token configurations

Affected if Webhook tokens are defined in job configurations or system settings
Identify token validation endpoints in use

Review the jobs using the Generic Webhook Trigger and identify which ones rely on token-based authentication for webhook triggers

Affected if Jobs use the 'Token' field to secure webhook endpoints

You are affected if the installed Generic Webhook Trigger Plugin version is 1.84.1 or earlier AND you have configured webhook tokens for trigger authentication.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 1.84.2 or later

Fixed in 1.84.2

Interim mitigation

Upgrade to Jenkins Generic Webhook Trigger Plugin version 1.84.2 or later which implements constant-time comparison for token validation.

Recommended fix High confidence

1.84.2

Log in to Jenkins as an administrator
Navigate to 'Manage Jenkins' > 'Manage Plugins'
Click on the 'Updates' tab
Locate 'Generic Webhook Trigger Plugin' in the list
If version 1.84.2 or later is available, select the plugin and click 'Download now and install after restart'
Alternatively, go to the 'Available' tab, search for 'Generic Webhook Trigger', and install or update to version 1.84.2
After installation, restart Jenkins to apply the update
Verify the plugin version shows 1.84.2 or later in 'Manage Plugins' > 'Installed' tab

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

Fix this in Generic Webhook Trigger Scoped from the published advisory

Consultation2.0 h
Implementation1.0 h
Testing2.0 h
Review / QA1.0 h

6.0 hours of engineering $1,060

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,696.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

www.jenkins.ioVendor Advisory
www.openwall.comMailing ListThird Party Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-43412 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2022-43412?

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.

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

At a glance

A fix existsUpgrade to 1.84.2 or later

Severity 5.3 Medium

Exploit likelihood EPSS, next 30 days 0.5%

Affects: Generic Webhook Trigger

Remediation

Need this fixed?

Fix this in Generic Webhook Trigger 6 hrs · Moderate

Typical engagement from $1,060

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2022-43412 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References