dbcve.org
TraccarApplication

CVE-2023-50729

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-15
Fix available
A fix is available. Upgrade to 5.11 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Traccar is an open source GPS tracking system. Prior to 5.11, Traccar is affected by an unrestricted file upload vulnerability in File feature allows attackers to execute arbitrary code on the server. This vulnerability is more prevalent because Traccar is recommended to run web servers as root user. It is also more dangerous because it can write or overwrite files in arbitrary locations. Version 5.11 was published to fix this vulnerability.

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 · moderate confidence

Unrestricted file upload vulnerability in Traccar's File feature (versions prior to 5.11) allows attackers to write files to arbitrary locations on the server, leading to arbitrary code execution. The vulnerability is exacerbated by Traccar's common practice of running as root, enabling full filesystem access.

MitigationUpgrade to Traccar version 5.11 or later immediately. As a compensating control, ensure the application does not run as root and restrict file system permissions to limit write access to authorized directories.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TraccarApplication
Affected:< 5.11

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Traccar installation and version
    Locate the Traccar installation directory (commonly /opt/traccar or /usr/share/traccar). Check for a version file or examine the traccar.jar/manifest for version information. If running as a service, use 'systemctl status traccar' or check process command line arguments.
    Affected if Installed version is prior to 5.11 (e.g., 5.10, 5.9, etc.)
  2. Verify Traccar is running as root
    Check the running Traccar process user: run 'ps aux | grep traccar' or 'id <traccar-user>' if the process is identified. Also check /etc/passwd for the traccar user entry and its login shell or UID.
    Affected if The Traccar process runs with UID 0 (root) or as a user with elevated filesystem permissions
  3. Confirm File feature is accessible
    Access the Traccar web interface and navigate to the File feature (typically under Administration or Settings sections). Alternatively, check the traccar.xml configuration file for any file-related device communication or file storage settings that may be enabled.
    Affected if The File feature is enabled or accessible via the web interface or API without additional access controls

Environment is affected if Traccar version is below 5.11, the File feature is enabled/accessible, and the application runs with root privileges or elevated filesystem access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 5.11 or later
Fixed in 5.11
Interim mitigation

Upgrade to Traccar version 5.11 or later immediately. As a compensating control, ensure the application does not run as root and restrict file system permissions to limit write access to authorized directories.

Recommended fix High confidence

Traccar 5.11

  1. Back up the current Traccar installation including database and configuration files
  2. Stop the Traccar service
  3. Download Traccar version 5.11 from the official Traccar repository
  4. Replace the existing Traccar files with the new version 5.11 files
  5. Verify file permissions are correct after the upgrade (note: Traccar is often run as root which increases severity)
  6. Start the Traccar service
  7. Verify the application is functioning correctly and the File feature no longer allows unrestricted file uploads
Caveat Review the 5.11 release notes for any configuration changes or database schema updates that may require attention

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Traccar Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-50729 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-50729 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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