China Linked Hackers Exploit MONAI Label Zero Day in Medical Software

3 min read
China Linked Hackers Exploit MONAI Label Zero Day in Medical Software

Discovery of a Critical Weakness in MONAI Label

Security researchers reported that a sophisticated threat group identified a severe flaw in MONAI Label, an open source platform used for annotating medical images. The flaw allows unauthorised code execution on systems that run the software, creating a direct pathway to sensitive health information.

What Is MONAI Label?

MONAI Label is part of the Medical Open Network for AI ecosystem, providing clinicians with tools to label imaging data quickly. It is widely adopted in hospitals and research institutions because it integrates with popular picture archiving systems.

Technical Details of the Zero Day

The vulnerability resides in the way MONAI Label processes input files. By supplying a crafted image file, an attacker can trigger a buffer overflow that leads to remote code execution. The issue was catalogued as CVE‑2024‑XXXXX by the National Vulnerability Database.

Attackers’ Methodology

According to the report, the actors employed autonomous software agents developed by a group known as Cairn. These agents performed automated reconnaissance, identified vulnerable installations, and delivered malicious payloads without human intervention.

Step‑by‑step Attack Flow

  1. Scanning of public IP ranges for servers running MONAI Label.
  2. Verification of the vulnerable version by sending test files.
  3. Deployment of a payload that establishes a backdoor connection.
  4. Extraction of stored medical images and patient identifiers.

Why the Attack Was Effective

The automation allowed the group to compromise dozens of systems in a short period. Because many installations are not regularly patched, the agents could operate silently, avoiding detection by conventional antivirus tools.

Potential Impact on Healthcare Providers

Compromise of MONAI Label can lead to several serious outcomes:

  • Unauthorised access to radiology images and associated reports.
  • Manipulation of annotation data, potentially affecting diagnostic AI models.
  • Exposure of personal health information, violating privacy regulations.
  • Disruption of clinical workflows, causing delays in patient care.

Regulatory bodies such as the U.S. Food and Drug Administration have warned that vulnerabilities in medical software can pose direct risks to patient safety.

Response from Vendors and Authorities

Amazon, which hosts many cloud‑based deployments of MONAI Label, issued an advisory urging customers to apply the latest security patch. The advisory can be found on the official Amazon security blog.

The United States Computer Emergency Readiness Team (US‑CERT) added the vulnerability to its National Cyber Awareness System, recommending immediate mitigation steps for healthcare organisations.

Mitigation Recommendations

Healthcare IT teams should consider the following actions:

  1. Update MONAI Label to the patched version released on 2024‑09‑15.
  2. Restrict network access to MONAI services using firewalls and zero trust principles.
  3. Implement continuous monitoring for unusual file uploads or outbound connections.
  4. Conduct regular vulnerability scans against medical imaging infrastructure.
  5. Educate staff about the risks of downloading unauthorised image files.

Adopting these measures aligns with guidance from the National Institute of Standards and Technology on securing health information systems.

Broader Implications for Medical Software Security

The incident underscores the growing convergence of cyber threats and healthcare technology. As more clinical tools rely on open source components, attackers are increasingly targeting the supply chain to gain footholds in hospitals.

Experts argue that the industry must shift from reactive patching to proactive security design, incorporating threat modelling and regular code audits for critical applications.

For more information on securing medical devices, refer to the FDA’s guidance on cybersecurity in the post‑market phase.

Comments

No comments yet. Be first.

More from this author