# CVE-2024-24809: Traccar vulnerable to Path Traversal: 'dir/../../filename' and Unrestricted Upload of File with Dangerous Type

> Attackers can upload malicious files via path traversal to execute arbitrary commands or perform XSS, affecting Traccar GPS tracking systems.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Apr 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-vhrw-72f6-gwp5

## What is CVE-2024-24809?

CVE-2024-24809 is a high-severity vulnerability in traccar, published on 10 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Traccar is an open source GPS tracking system. Versions prior to 6.0 are vulnerable to path traversal and unrestricted upload of file with dangerous type. Since the system allows registration by default, attackers can acquire ordinary user permissions by registering an account and exploit this vulnerability to upload files with the prefix `device.` under any folder. Attackers can use this vulnerability for phishing, cross-site scripting attacks, and potentially execute arbitrary commands on the server. Version 6.0 contains a patch for the issue.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-27 (Path Traversal: 'dir/../../filename')

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


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

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

## Is CVE-2024-24809 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-24809 exists.

Public exploit code:

- Critical Flaws in Traccar GPS System Expose Users to Remote Attacks (github_poc): https://github.com/gh-ost00/CVE-2024-24809-Proof-of-concept
- Traccar v5 Remote Code Execution (CVE-2024-31214 and CVE-2024-24809) (metasploit)
- Palo Alto Expedition Remote Code Execution (CVE-2024-5910 and CVE-2024-9464) (metasploit)
- Traccar - Unrestricted File Upload (nuclei): http/cves/2024/CVE-2024-24809.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2024-24809 is a high-severity vulnerability in traccar, published on 10 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-24809 exists.

Affected product: traccar. 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-24809/ (Markdown: https://insights.sbomify.com/CVE-2024-24809/index.md)
```

## Sources

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

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