CVE-2024-14037
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedRedsea Cloud eHR contains an arbitrary file upload vulnerability that allows unauthenticated attackers to achieve remote code execution by uploading malicious files through the PtFjk.mob servlet endpoint. Attackers can submit a multipart POST request with a JSP webshell disguised using a spoofed image/jpeg Content-Type to bypass the absence of extension and MIME type validation, with the uploaded file stored at a predictable path under the uploadfile directory and executed directly by the web server. Exploitation evidence was first observed by the Shadowserver Foundation on 2024-11-03 (UTC).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceRedsea Cloud eHR suffers from an unauthenticated arbitrary file upload vulnerability in the PtFjk.mob servlet. Attackers bypass missing validation by spoofing the Content-Type as image/jpeg while uploading JSP webshells, which are stored in a predictable location under the uploadfile directory and directly executed by the web server, achieving remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Redsea Cloud eHR is deployedSearch for files, directories, or services associated with Redsea Cloud eHR. Check for the PtFjk.mob servlet path (typically at /PtFjk.mob or within the eHR web application context).Affected if The PtFjk.mob servlet is found and accessible in your environment.
-
Verify the uploadfile directory existsLocate the uploadfile directory within the web application's document root or deployment folder. Common paths may include <webapp>/uploadfile/ or similar.Affected if The uploadfile directory exists and is writable by the web application.
-
Inspect uploadfile directory for unexpected JSP filesList all files in the uploadfile directory. Look for any .jsp files that were not intentionally uploaded through legitimate business functions.Affected if Any JSP files are present in the uploadfile directory that were not explicitly uploaded by administrators.
-
Review web server or application logs for PtFjk.mob requestsSearch access logs for POST requests to /PtFjk.mob or similar paths. Look for requests with Content-Type: image/jpeg that contain JSP code in the multipart body.
-
Check for unauthorized remote code executionExamine the web application for newly created or modified JSP files outside the expected deployment directories. Look for webshell patterns (base64_decode, cmd, exec, Runtime.getRuntime()).
You are affected if the PtFjk.mob servlet is accessible in your Redsea Cloud eHR deployment and any JSP files exist in the uploadfile directory or suspicious POST requests to PtFjk.mob appear in your logs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict server-side file validation (extension allowlist, Magic bytes/content validation), store uploads outside the webroot or disable script execution in the upload directory, and remove the vulnerable servlet or restrict access if the upload functionality is unnecessary.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-14037 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-14037 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data