# CVE-2024-31214: Traccar's unrestricted file upload vulnerability in device image upload could lead to remote code execution

> Attackers can upload arbitrary files via the device image API to achieve remote code execution, especially in default configurations with self-registration enabled.

- **Severity:** Critical 9.7 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-3gxq-f2qj-c8v9

## What is CVE-2024-31214?

CVE-2024-31214 is a critical vulnerability in traccar, published on 10 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Traccar is an open source GPS tracking system. Traccar versions 5.1 through 5.12 allow arbitrary files to be uploaded through the device image upload API. Attackers have full control over the file contents, full control over the directory where the file is stored, full control over the file extension, and partial control over the file name. While it's not  for an attacker to overwrite an existing file, an attacker can create new files with certain names and attacker-controlled extensions anywhere on the file system. This can potentially lead to remote code execution, XSS, DOS, etc. The default install of Traccar makes this vulnerability more severe. Self-registration is enabled by default, allowing anyone to create an account to exploit this vulnerability. Traccar also runs by default with root/system privileges, allowing files to be placed anywhere on the file system. Version 6.0 contains a fix for the issue. One may also turn off self-registration by default, as that would make most vulnerabilities in the application much harder to exploit by default and reduce the severity considerably.

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

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

It affects 1 product.


Products: Traccar Traccar.

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

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

## Is CVE-2024-31214 being exploited?

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

Public exploit code:

- Traccar v5 Remote Code Execution (CVE-2024-31214 and CVE-2024-24809) (metasploit)

## Other vulnerabilities in traccar

- [CVE-2024-7746](https://insights.sbomify.com/CVE-2024-7746/): Use of default credentials at Traccar fleet management solution (critical 9.5)
- [CVE-2026-25648](https://insights.sbomify.com/CVE-2026-25648/): Traccar Vulnerable to Stored Cross-Site Scripting (XSS) via Malicious SVG File Upload (high 8.7)
- [CVE-2023-50729](https://insights.sbomify.com/CVE-2023-50729/): An unrestricted file upload vulnerability in traccar leads to RCE (high 8.5)
- [CVE-2020-5246](https://insights.sbomify.com/CVE-2020-5246/): LDAP injection vulnerability in Traccar GPS Tracking System (high 7.7)
- [CVE-2026-25649](https://insights.sbomify.com/CVE-2026-25649/): Traccar Vulnerable to Authorization Code Theft via Open Redirect in OIDC Provider Endpoints (high 7.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-31214 is a critical vulnerability in traccar, published on 10 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-31214 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-31214/ (Markdown: https://insights.sbomify.com/CVE-2024-31214/index.md)
```

## Sources

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

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