# CVE-2024-41605: Security feature bypass in n/a

> Attackers can execute arbitrary code by replacing update files due to missing integrity validation in Foxit PDF Reader and Editor.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2024
- **Updated:** 27 Sep 2024
- **Also known as:** GHSA-mrhc-m9q7-2fvp

## What is CVE-2024-41605?

CVE-2024-41605 is a high-severity vulnerability in n/a, published on 26 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Foxit PDF Reader before 2024.3, and PDF Editor before 2024.3 and 13.x before 13.1.4, an attacker can replace an update file with a Trojan horse via side loading, because the update service lacks integrity validation for the updater. Attacker-controlled code may thus be executed.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2024-41605 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-41605 is a high-severity vulnerability in n/a, published on 26 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-41605 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-41605/ (Markdown: https://insights.sbomify.com/CVE-2024-41605/index.md)
```

## Sources

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

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