Msteams Webhook TriggerApplication · Jenkins
CVE-2023-46658
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 MSTeams Webhook Trigger Plugin 0.1.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 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 MSTeams Webhook Trigger Plugin versions 0.1.1 and earlier uses a non-constant time comparison function when validating webhook tokens. This timing side-channel allows attackers to perform statistical analysis of response times to deduce the correct token character by character, potentially enabling full token extraction through repeated requests.
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
Msteams Webhook TriggerApplication
= 0.1.0= 0.1.1CVSS 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.
-
Verify the MSTeams Webhook Trigger plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: jenkins-cli.jar who-am-i or REST API /api/pluginManager/plugin/msteams-webhook-trigger to query installed pluginsAffected if The plugin named MSTeams Webhook Trigger appears in the installed plugins list
-
Determine the installed version of the pluginIn the Manage Plugins > Installed tab, locate the MSTeams Webhook Trigger plugin and note the Version column. Alternatively, check the manifest file: $JENKINS_HOME/plugins/msteams-webhook-trigger/META-INF/MANIFEST.MFAffected if The version is 0.1.0 or 0.1.1 exactly
-
Check if webhook triggers are configuredNavigate to Jenkins > Manage Jenkins > System and look for MSTeams Webhook configuration, or review job configurations for MSTEAMS_WEBHOOK token/string fields. Check job configuration XML files in $JENKINS_HOME/jobs/ for MsteamsWebhookTrigger elementsAffected if Any Jenkins job or system configuration contains an MSTeams Webhook Trigger with a configured token endpoint
You are affected if the MSTeams Webhook Trigger plugin version 0.1.0 or 0.1.1 is installed and a webhook trigger with a token is configured in your Jenkins environment.
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 dataReplace the token comparison with a constant-time comparison function (e.g., Java's MessageDigest.isEqual) to prevent timing attacks. Upgrade to plugin version 0.1.2 or later if available.
Fix this in Msteams Webhook Trigger
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46658 — 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-2023-46658 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