External Monitor Job TypeApplication · Jenkins
CVE-2023-37942
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 External Monitor Job Type Plugin 206.v9a_94ff0b_4a_10 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.
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 External Monitor Job Type Plugin versions 206.v9a_94ff0b_4a_10 and earlier contains an XML External Entity (XXE) vulnerability due to its XML parser not being configured to disable external entity processing. This allows attackers with Job/Create permissions to potentially read local files or perform server-side request forgery (SSRF) attacks by submitting specially crafted XML content.
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
External Monitor Job TypeApplication
<= 206.v9a_94ff0b_4a_10CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 External Monitor Job Type Plugin is installedIn the Jenkins web interface, go to Manage Jenkins > Manage Plugins > Installed. Search for 'External Monitor Job Type' in the list of installed plugins.Affected if The plugin appears in the installed plugins list.
-
Check the installed plugin versionIn the plugin manager's Installed tab, locate the External Monitor Job Type Plugin and note the version number displayed in the Version column.Affected if The version is 206.v9a_94ff0b_4a_10 or earlier.
-
Review Job/Create permission assignmentsGo to Manage Jenkins > Manage and Assign Roles > Assign Roles (or Manage Users if using matrix authorization). Check which users or groups have the Job/Create permission enabled.Affected if Job/Create permission is granted to users who are not fully trusted.
-
Inspect XML job configuration submissionsIf external monitor jobs can be created via the UI at New Item > External Monitor Job, note that submitting XML content in job configurations triggers the vulnerable XML parsing.Affected if External Monitor Job creation is permitted and untrusted users can configure these jobs.
You are affected if the External Monitor Job Type Plugin is installed at version 206.v9a_94ff0b_4a_10 or earlier AND untrusted users have Job/Create permissions.
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 External Monitor Job Type Plugin to version 207.v5a_2ff1b_6a_b_4 or later, which properly configures the XML parser to prevent XXE attacks. As a compensating control, restrict Job/Create permissions to trusted users only.
Fix this in External Monitor Job Type
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-37942 — 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-37942 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