Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2024-14037 – Unauthenticated RCE via Arbitrary File Upload – Red Sea Cloud eHR (All Versions)

Be the first to know when new zero-days emerge:

Summary

CVE-2024-14037 is a critical unauthenticated arbitrary file upload vulnerability (CWE-434) in Red Sea Cloud eHR, a Java servlet-based HR management platform developed by Guangzhou Red Sea Cloud Computing Co., Ltd. An unauthenticated remote attacker can upload a malicious JSP webshell through an exposed servlet endpoint and execute it directly on the server, achieving full Remote Code Execution (RCE). The vulnerability carries a CVSS v4.0 score of 9.3 (Critical) and active in-the-wild exploitation has been confirmed since November 2024.

Technical details

  • Root cause: The /RedseaPlatform/PtFjk.mob?method=upload servlet endpoint accepts multipart POST file uploads with no authentication check and performs no validation of file extension or MIME type, allowing any file type to be stored on the server.
  • Trigger conditions: No authentication, credentials, or user interaction is required. The endpoint is reachable over the internet on any exposed eHR deployment.
  • Attack vector: An attacker submits a crafted multipart POST request to the vulnerable endpoint, disguising a JSP webshell as an image by spoofing the Content-Type: image/jpeg header. The server stores the uploaded file at a predictable path under the uploadfile directory.
  • Impact: The uploaded webshell is executed directly by the Java web server, granting the attacker full unauthenticated Remote Code Execution (RCE) on the underlying host. Confidentiality, integrity, and availability of the server are all fully compromised. Exploitation evidence was first observed by the Shadowserver Foundation on 2024-11-03 (UTC), and multiple public proof-of-concept repositories document the exact technique.

Affected software

  • Guangzhou Red Sea Cloud Computing Co., Ltd. — Red Sea Cloud eHR: All versions

Severity

| Standard | Score | Rating | Vector |
|—|—|—|—|
| CVSS v4.0 | 9.3 | Critical | AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
| CVSS v3.1 | 9.8 | Critical | AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |

Mitigation and recommended actions

  • Vendor patch: No official patch or fixed version has been publicly released by Guangzhou Red Sea Cloud Computing Co., Ltd. at this time. Organizations should contact the vendor directly for remediation guidance.
  • Immediate workarounds:
    • Block the vulnerable endpoint at the network or WAF layer: Restrict or deny external access to /RedseaPlatform/PtFjk.mob and the uploadfile directory via firewall rules or a web application firewall.
    • Restrict network exposure: If Red Sea Cloud eHR does not require public internet access, immediately place the application behind a VPN or restrict access to trusted IP ranges only.
    • Monitor for exploitation indicators: Review web server logs for POST requests targeting /RedseaPlatform/PtFjk.mob?method=upload and inspect the uploadfile directory for any unexpected .jsp or script files.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge