CVE-2023-3892 [Medium] | Security Vulnerability in Assistant

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-03-17	0.04%	0.07%	+0.03%
2	2023-09-20	—	0.04%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-03-17

0.04%

0.07%

+0.03%

2023-09-20

—

0.04%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.6	3.1	MEDIUM	`CVSS:3.1/AV:A/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:H` Click to expand Attack vector (AV:A) Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	0.9	4.7	[email protected]
7.4	3.1	HIGH	`CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:A) Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.5	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.6

3.1

MEDIUM

CVSS:3.1/AV:A/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:H Click to expand

Attack vector (AV:A): Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

0.9

4.7

[email protected]

7.4

3.1

HIGH

CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:A): Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.5

5.9

[email protected]

Affected software / configurations for CVE-2023-3892

Vendor	Product	Version	Raw CPE
mimsoftware	assistant	7.2.10	cpe:2.3:a:mimsoftware:assistant:7.2.10:::::::*
mimsoftware	assistant	7.3.3	cpe:2.3:a:mimsoftware:assistant:7.3.3:::::::*
mimsoftware	client	7.2.10	cpe:2.3:a:mimsoftware:client:7.2.10:::::::*
mimsoftware	client	7.3.3	cpe:2.3:a:mimsoftware:client:7.3.3:::::::*

References for CVE-2023-3892

URL	Tags
https://www.mimsoftware.com/cve-2023-3892	Vendor Advisory

URL

CVE-2023-3892 | Unsafe XML parsing of 3rd party DICOM private tags may lead to XXE

Exploit prediction scoring system (EPSS) score for CVE-2023-3892

Common vulnerability scoring system (CVSS) metrics for CVE-2023-3892

Weakness enumeration for CVE-2023-3892

Affected software / configurations for CVE-2023-3892

References for CVE-2023-3892