MercurialApplication · Jenkins
CVE-2022-43410
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 Mercurial Plugin 1251.va_b_121f184902 and earlier provides information about which jobs were triggered or scheduled for polling through its webhook endpoint, including jobs the user has no permission to access.
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 confidenceJenkins Mercurial Plugin versions 1251.va_b_121f184902 and earlier contains an information disclosure vulnerability in its webhook endpoint. The endpoint reveals which jobs were triggered or scheduled for polling, including job names and activity for jobs the requesting user has no permission to access. This allows unauthorized users to enumerate existing jobs and their status.
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
MercurialApplication
<= 1251.va_b_121f184902CVSS 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 Mercurial Plugin installation and versionIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and locate the Mercurial Plugin. Note the version number displayed.Affected if The installed version is 1251.va_b_121f184902 or earlier, or the version field is empty/unavailable indicating an unpatched installation.
-
Confirm webhook endpoint configurationReview Jenkins system configuration or job configurations that use Mercurial. Look for webhook-related settings or URL endpoints configured for Mercurial repositories.Affected if A webhook endpoint is configured and exposed for Mercurial polling or triggering.
-
Verify access control on webhook pathExamine the Jenkins authorization matrix or global security settings. Test accessing the Mercurial webhook URL path (typically under /mercurial/ or similar webhook endpoint) using an account with limited or no permissions.Affected if The webhook endpoint returns job names, polling status, or triggered job information to users who lack permission to view those jobs.
The environment is affected if the Jenkins Mercurial Plugin version is 1251.va_b_121f184902 or earlier AND the webhook endpoint is accessible to unauthorized or low-privilege users, allowing job enumeration.
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 to the patched version of the Jenkins Mercurial Plugin when available, or implement proper access controls on the webhook endpoint to prevent unauthorized job information disclosure.
Fix this in Mercurial
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43410 — 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-43410 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