SourcemonitorApplication · Jenkins
CVE-2022-45396
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 SourceMonitor Plugin 0.2 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 SourceMonitor Plugin versions 0.2 and earlier fails to securely configure its XML parser, enabling XML External Entity (XXE) attacks. This allows attackers to inject malicious XML containing external entity references to exfiltrate sensitive data or perform server-side request forgery (SSRF) by leveraging the parser's ability to process external DTDs and entities.
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
SourcemonitorApplication
<= 0.2CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 SourceMonitor Plugin is installedIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed and look for SourceMonitor Plugin in the list. Note the installed version.Affected if The plugin is installed and the version is 0.2 or earlier.
-
Identify the plugin configuration fileLocate the SourceMonitor Plugin configuration in the Jenkins home directory under plugins/sourcemonitor or within the plugin's WEB-INF. Look for XML parser configuration in the plugin's Java source code or configuration files.Affected if The plugin configuration does not explicitly disable external entities and DTDs in the XML parser setup.
-
Check for secure XML parser initializationInspect the plugin's code for XMLParser creation. Look for features such as 'XMLConstants.ACCESS_EXTERNAL_DTD', 'XMLConstants.ACCESS_EXTERNAL_SCHEMA', and 'javax.xml.XMLConstants.FEATURE_SECURE_PROCESSING'. These should be explicitly set to restrict external access.Affected if The XML parser is initialized without disabling external entity processing or without setting secure processing features.
-
Verify XML input handlingDetermine if the plugin processes XML files from user-uploaded sources, version control repositories, or external CI/CD inputs. Check if untrusted XML is parsed without sanitization.Affected if The plugin parses XML from untrusted sources and the parser is not configured to prevent XXE.
You are affected if the SourceMonitor Plugin version is 0.2 or earlier and the plugin processes XML files without secure parser configuration that disables external entities and DTDs.
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 SourceMonitor Plugin to a version that configures the XML parser to disable external entities and DTDs, or apply a fix that sets the parser features to prevent XXE exploitation.
Fix this in Sourcemonitor
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45396 — 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-45396 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