dbcve.org
J WbemApplication · Ws Inc

CVE-2023-37364

CRITICAL · 9.1 CVSS v3.1 Published 2023-08-03
Fix available
A fix is available. Upgrade to 4.7.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
In WS-Inc J WBEM Server 4.7.4 before 4.7.5, the CIM-XML protocol adapter does not disable entity resolution. This allows context-dependent attackers to read arbitrary files or cause a denial of service, a similar issue to CVE-2013-4152.

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 confidence

The J WBEM Server CIM-XML protocol adapter fails to disable XML external entity resolution, enabling attackers to craft malicious XML requests that exploit XXE (XML External Entity) injection. This allows unauthorized file disclosure from the server filesystem and potential denial of service via recursive entity expansion attacks.

MitigationUpgrade to J WBEM Server version 4.7.5 or later which properly disables entity resolution in the CIM-XML adapter; alternatively, configure the underlying XML parser to prohibit external entity processing as an interim workaround.

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
J WbemApplication
Affected:>= 4.0.0, < 4.7.5

CVSS 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
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify J WBEM Server installation and version
    Locate the J WBEM Server installation directory and check the version information file or product metadata. Common locations include /opt/jwbem or the installation root directory. Look for a version manifest, about file, or product-info file that displays the installed version number.
    Affected if The installed version is 4.0.0 or higher but lower than 4.7.5
  2. Confirm CIM-XML protocol adapter is in use
    Inspect the J WBEM Server configuration files to determine whether the CIM-XML protocol adapter is enabled. Check for CIM-XML related configuration entries in the main configuration file (typically named jwbem.properties, config.xml, or similar) or in a dedicated CIM-XML adapter configuration section.
    Affected if The CIM-XML adapter is explicitly enabled or configured in the J WBEM Server configuration
  3. Locate XML parser configuration for the CIM-XML adapter
    Examine the CIM-XML adapter configuration and related XML processing settings. Look for XML parser configuration files, properties, or parameters that control external entity resolution. Check for any XML-related settings that may reference entity processing, DTD handling, or external entity configuration.
    Affected if XML parser settings allow external entity processing or do not explicitly disable XXE vulnerability
  4. Verify external entity resolution is disabled
    Review the XML parser or CIM-XML adapter configuration for settings related to external entity resolution. Specifically look for parameters like 'external-entities', 'entity-resolver', 'xxe-protection', or similar security-related XML configuration flags. Confirm whether these settings explicitly disable external entity processing.
    Affected if External entity resolution is not explicitly disabled or is set to allow external entities

A user is affected if J WBEM Server version 4.0.0 through 4.7.4 is installed with the CIM-XML adapter enabled and XML external entity resolution is not explicitly disabled in the parser configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 4.7.5 or later
Fixed in 4.7.5
Interim mitigation

Upgrade to J WBEM Server version 4.7.5 or later which properly disables entity resolution in the CIM-XML adapter; alternatively, configure the underlying XML parser to prohibit external entity processing as an interim workaround.

Recommended fix High confidence

4.7.5 or later

  1. 1. Identify all instances of WS-Inc J WBEM Server currently running versions >= 4.0.0 and < 4.7.5
  2. 2. Schedule a maintenance window for the upgrade
  3. 3. Back up the current J WBEM Server configuration and data
  4. 4. Download J WBEM Server version 4.7.5 or later from the vendor
  5. 5. Stop the J WBEM Server service
  6. 6. Install version 4.7.5 following the vendor's upgrade instructions
  7. 7. Verify the CIM-XML protocol adapter configuration has entity resolution disabled
  8. 8. Start the J WBEM Server service

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in J Wbem Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-37364 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-37364 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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