Osf Builder Suite \Application · Jenkins
CVE-2022-45397
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 OSF Builder Suite : : XML Linter Plugin 1.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 OSF Builder Suite XML Linter Plugin versions 1.0.2 and earlier contains a critical XML External Entity (XXE) vulnerability due to its XML parser not being configured to prevent XXE attacks. An attacker could exploit this by submitting malicious XML documents containing external entity references, potentially allowing file disclosure, server-side request forgery (SSRF), or denial of service.
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
Osf Builder Suite \Application
<= 1.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 the OSF Builder Suite XML Linter Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed and search for 'OSF Builder Suite XML Linter' or 'osf-xml-linter' to confirm the plugin is present.Affected if The plugin appears in the installed plugins list.
-
Identify the installed plugin versionIn the Installed Plugins page, locate the OSF Builder Suite XML Linter Plugin and note the Version column. Compare this version against the affected range: 1.0.2 and earlier.Affected if The installed version is 1.0.2 or any version lower (e.g., 1.0.1, 1.0.0).
-
Check for XML Linter job configurationsSearch Jenkins jobs (via Manage Jenkins > Manage Users or directly in job configurations) for uses of the XML Linter functionality. Look for build steps or post-build actions referencing the OSF XML Linter or XML linting features.Affected if Any job is configured to use the XML Linter build step or post-build action.
-
Determine if the plugin is enabledGo to Manage Jenkins > Configure Global Security or Manage Plugins > Installed and verify whether the OSF Builder Suite XML Linter Plugin is disabled or has its XML processing features actively available.Affected if The plugin is enabled and its XML processing features are available for job configurations.
The environment is affected if the OSF Builder Suite XML Linter Plugin version 1.0.2 or earlier is installed, enabled, and its XML Linter feature is being used in any job configuration.
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 plugin to a version that properly configures the XML parser to disable external entities and DOCTYPE declarations, or implement secure XML parser configuration with features like XMLConstants.ACCESS_EXTERNAL_DTD and XMLConstants.ACCESS_EXTERNAL_SCHEMA set to empty strings.
Fix this in Osf Builder Suite \
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45397 — 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-45397 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