dbcve.org
Tsclinical Define.xml GeneratorApplication · Fujitsu

CVE-2023-22377

HIGH · 7.4 CVSS v3.1 Published 2023-02-15
Fix available
A fix is available. Upgrade to 1.1.1 or later.
See remediation →
83/100
Remediation priority · High
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
Improper restriction of XML external entity reference (XXE) vulnerability exists in tsClinical Define.xml Generator all versions (v1.0.0 to v1.4.0) and tsClinical Metadata Desktop Tools Version 1.0.3 to Version 1.1.0. If this vulnerability is exploited, an attacker may obtain an arbitrary file which meets a certain condition by reading a specially crafted XML file.

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

XXE (XML External Entity) vulnerability in tsClinical Define.xml Generator (v1.0.0-v1.4.0) and Metadata Desktop Tools (v1.0.3-v1.1.0) allows attackers to read arbitrary files by supplying specially crafted XML files with external entity references that the vulnerable XML parser processes without restriction.

MitigationDisable external entity processing and DTD parsing in the application's XML parser configuration; if a patched version is available, upgrade to that version.

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
Tsclinical Define.xml GeneratorApplication
Affected:>= 1.0.0, <= 1.4.0
Tsclinical Metadata Desktop ToolsApplication
Affected:>= 1.0.3, < 1.1.1

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

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

  1. Identify installed Tsclinical product
    Locate Fujitsu Tsclinical Define.xml Generator or Metadata Desktop Tools installation on the system. Check program files, application directories, or use system inventory tools to confirm which product is present.
    Affected if Either Fujitsu Tsclinical Define.xml Generator or Metadata Desktop Tools is installed
  2. Determine installed version
    Access the application's About section, version info in the executable properties, or check installation directories for version manifest files. Common locations include the application root directory or Windows registry entries for installed software.
    Affected if Version cannot be determined or falls within affected ranges
  3. Compare version against affected ranges
    For Define.xml Generator: check if version is >= 1.0.0 and <= 1.4.0. For Metadata Desktop Tools: check if version is >= 1.0.3 and <= 1.1.0.
    Affected if Version falls within 1.0.0-1.4.0 for Define.xml Generator OR 1.0.3-1.1.0 for Metadata Desktop Tools
  4. Confirm XML file processing is used
    Determine if the application is used to import, parse, or generate XML files, particularly Define.xml files. XXE exploits require the application to process untrusted XML input.
    Affected if The application processes XML files from external or untrusted sources

If the installed product version falls within the affected ranges AND the application is used to process XML files, the environment is vulnerable to CVE-2023-22377.

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 1.1.1 or later
Fixed in 1.1.1
Interim mitigation

Disable external entity processing and DTD parsing in the application's XML parser configuration; if a patched version is available, upgrade to that version.

Recommended fix Moderate confidence

Tsclinical Define.xml Generator: >= 1.4.1; Tsclinical Metadata Desktop Tools: >= 1.1.1

  1. 1. For Tsclinical Define.xml Generator: Upgrade to version 1.4.1 or later (the next release after the last affected version 1.4.0)
  2. 2. For Tsclinical Metadata Desktop Tools: Upgrade to version 1.1.1 or later (which is the first version beyond the affected range < 1.1.1)
  3. 3. After upgrading, verify that the Define.xml Generator and Metadata Desktop Tools applications start without errors
  4. 4. Test parsing of legitimate XML files to confirm functionality is preserved
  5. 5. Ensure the upgraded versions are used for processing any new XML files
Caveat Minimal risk - patch release intended to fix security issue without changing core functionality; verify custom configurations work with new version

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

Fix this in Tsclinical Define.xml Generator Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-22377 — 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-22377 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