# CVE-2024-35593: File upload in n/a

> Attackers can execute arbitrary code by uploading a crafted PDF file via the File preview function in Raingad IM.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 May 2024
- **Updated:** 13 Feb 2025

## What is CVE-2024-35593?

CVE-2024-35593 is a medium-severity vulnerability in n/a, published on 24 May 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An arbitrary file upload vulnerability in the File preview function of Raingad IM v4.1.4 allows attackers to execute arbitrary code via uploading a crafted PDF file.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2024-35593?


## How do I fix CVE-2024-35593?

No fix has been published for CVE-2024-35593 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-35593 being exploited?

There is no known exploitation of CVE-2024-35593 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-35593 and fix it if it is affected.

What it is: CVE-2024-35593 is a medium-severity vulnerability in n/a, published on 24 May 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-35593 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-35593/ (Markdown: https://insights.sbomify.com/CVE-2024-35593/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-35593
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-35593
- OSV: https://osv.dev/vulnerability/CVE-2024-35593

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-35593/
Summaries are generated and may contain mistakes; the official description above is the record.