S4E just found a high top 10 tcp port service scan
critical·Product Based Web Vulnerabilities·Updated May 23, 2025

CVE-2018-19276 Scanner

Targets the REST API endpoint that deserializes user-supplied data, allowing an attacker to execute arbitrary code on the server.

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
3k
Times Used
continuous scan runs
3.4k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2018-19276
9.8
CVSScritical
Exploitable remotely over the internet · no authentication required.

OpenMRS before 2.24.0 is affected by an Insecure Object Deserialization vulnerability that allows an unauthenticated user to execute arbitrary commands on the targeted system via crafted XML data in a request body.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
n/aby n/a
n/a
Updated Aug 21, 2026View on NVD →
Detail

OpenMRS is an open-source electronic medical record platform used by healthcare facilities in resource-limited settings to manage patient data, workflows, and clinical information. It is built on Java and supports modular extensions for customization.

CVE-2018-19276 is a critical deserialization of untrusted data vulnerability that occurs when OpenMRS processes serialized Java objects without proper validation. This flaw arises from the use of unsafe deserialization methods in the platform's core libraries.

The vulnerability is triggered via the REST API endpoint that accepts serialized objects, specifically in the module administration functionality. An attacker can craft a malicious serialized object that, when deserialized, executes arbitrary commands on the server.

If exploited, this vulnerability allows remote code execution with the privileges of the OpenMRS application, potentially leading to full system compromise, data theft, and disruption of healthcare services.

Solution Advice
  • Upgrade OpenMRS to version 2.24.0 or later, which includes a fix for this vulnerability.
  • Implement input validation and sanitization for all data received via REST API endpoints.
  • Use a whitelist of allowed classes for deserialization to prevent untrusted objects.
  • Apply the latest security patches and updates to the Java runtime environment.
  • Enable logging and monitoring for deserialization-related exceptions and suspicious activity.
  • Deploy a web application firewall (WAF) to filter malicious serialized payloads.
  • Conduct regular security audits and penetration testing on the OpenMRS instance.
  • Restrict network access to the OpenMRS server using firewalls and segmentation.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.