dbcve.org
AssistantApplication · Mimsoftware

CVE-2023-3892

HIGH · 7.4 CVSS v3.1 Published 2023-09-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated

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 vulnerability in MIM Assistant and Client DICOM RTst Loading modules allows XML Entity Linking / XML External Entities Blowup. In order to take advantage of this vulnerability, an attacker must craft a malicious XML document, embed this document into specific 3rd party private RTst metadata tags, transfer the now compromised DICOM object to MIM, and force MIM to archive and load the data. Users on either version are strongly encouraged to update to an unaffected version (7.2.11+, 7.3.4+). This issue was found and analyzed by MIM Software's internal security team.  We are unaware of any proof of concept or actual exploit available in the wild. For more information, visit https://www.mimsoftware.com/cve-2023-3892 https://www.mimsoftware.com/cve-2023-3892 This issue affects MIM Assistant: 7.2.10, 7.3.3; MIM Client: 7.2.10, 7.3.3.

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

This is an XXE (XML External Entity) vulnerability in MIM Assistant and Client's DICOM RTst Loading modules. The software improperly restricts XML external entity references when parsing DICOM objects containing malicious XML in private RTst metadata tags, potentially allowing attackers to access local files or cause denial-of-service through entity expansion.

MitigationUpdate MIM Assistant and Client to version 7.2.11 or higher, or 7.3.4 or higher. Avoid loading DICOM objects from untrusted sources until patched.

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
AssistantApplication
Affected:= 7.2.10= 7.3.3
ClientApplication
Affected:= 7.2.10= 7.3.3

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
Adjacent
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:L/UI:R/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 checks

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

  1. Identify installed MIM product
    Locate MIM Assistant or MIM Client installation on the system - check program directories or registry for Mimsoftware applications
    Affected if Either MIM Assistant or MIM Client is installed
  2. Determine installed version
    Check the version of the installed MIM software (typically available in the application, About dialog, or installation metadata)
    Affected if Version is exactly 7.2.10 or 7.3.3
  3. Check for DICOM RTst module usage
    Determine if the DICOM RTst (Radiotherapy Structure Set) loading functionality is in use - this module handles DICOM RT objects containing XML metadata
    Affected if DICOM RTst Loading module is accessible or used to import DICOM files
  4. Assess exposure to untrusted DICOM objects
    Identify whether the system loads DICOM objects from external or untrusted sources, or if users can import DICOM files into the application
    Affected if Users can import DICOM objects from sources outside the trusted network

A user is affected if they have MIM Assistant or Client version 7.2.10 or 7.3.3 installed AND use the DICOM RTst loading functionality with potentially untrusted DICOM files.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update MIM Assistant and Client to version 7.2.11 or higher, or 7.3.4 or higher. Avoid loading DICOM objects from untrusted sources until patched.

Recommended fix High confidence

7.2.11+ or 7.3.4+

  1. Download MIM Assistant version 7.2.11 or higher (or 7.3.4 or higher) from the official MIM Software website
  2. Install the updated version following the vendor's standard upgrade procedure
  3. Verify the installation completed successfully and the version number is correct

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

Fix this in Assistant Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,370
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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