LiveActive security incident?Get immediate response
CVE Record

CVE-2020-37120: Rubo DICOM Viewer 2.0 - Buffer Overflow (SEH)

Rubo DICOM Viewer 2.0 contains a buffer overflow vulnerability in the DICOM server name input field that allows attackers to overwrite Structured Exception Handler (SEH). Attackers can craft a malicious text file with carefully constructed payload to execute arbitrary code by overwriting SEH and triggering remote code execution.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Rubo DICOM Viewer 2.0 has a critical memory corruption flaw in the DICOM server name input field. A crafted text file can overwrite exception-handling data and may allow arbitrary code execution. This matters most where the viewer is installed on workstations handling medical imaging data.

Executive priority

Treat as high-priority if Rubo DICOM Viewer 2.0 exists in your environment. The flaw can allow code execution, and public exploit information exists. If the product is not present, no direct exposure is indicated by the provided sources.

Technical view

The issue is a stack-based buffer overflow, CWE-121, involving Structured Exception Handler overwrite in Rubo DICOM Viewer 2.0. The CVSS 3.1 score is 9.8. Public references describe arbitrary code execution via a malicious text file targeting the DICOM server name input field.

Likely exposure

Exposure is limited to environments running Rubo DICOM Viewer 2.0. Healthcare, radiology, imaging, or lab systems are the most likely locations. The source bundle does not identify other affected versions or products.

Exploitation context

A public ExploitDB entry exists, but the CVE is not listed as CISA KEV in the provided data. There is no cited evidence of active exploitation. The available description indicates exploitation uses a crafted text file and triggers memory corruption leading to code execution.

Researcher notes

Evidence is centered on Rubo DICOM Viewer 2.0, CWE-121, SEH overwrite, and public exploit publication. The bundle does not provide a vendor patch, fixed version, or active exploitation evidence. Avoid assuming broader Rubo product impact without additional vendor confirmation.

Mitigation direction

  • Identify and remove or replace Rubo DICOM Viewer 2.0 where possible.
  • Check Rubo Medical Imaging or trusted advisory sources for vendor guidance.
  • Restrict use of untrusted DICOM-related files and configuration inputs.
  • Isolate affected imaging workstations from unnecessary network access.
  • Run the viewer with least-privileged user accounts where feasible.

Validation and detection

  • Inventory endpoints for Rubo DICOM Viewer 2.0 installations.
  • Confirm whether the DICOM server name input feature is used.
  • Review security tools for crashes or suspicious activity around the viewer.
  • Verify vulnerable systems are removed, replaced, or risk-accepted.
  • Document compensating controls for any systems that must remain in service.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-121: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-37120 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2020-37120Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Rubo Medical ImagingRubo DICOM Viewer2.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-121 · source CWE mapping

Stack-based Buffer Overflow

Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.