{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-5246 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-5246 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-5246 is a high-severity vulnerability in Traccar, published on 14 Jul 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-5246 and fix it if it is affected.\n\nWhat it is: CVE-2020-5246 is a high-severity vulnerability in Traccar, published on 14 Jul 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-5246 in the wild and no public exploit code.\n\nAffected product: Traccar. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2020-5246/ (Markdown: https://insights.sbomify.com/CVE-2020-5246/index.md)","id":"CVE-2020-5246","markdown":"https://insights.sbomify.com/CVE-2020-5246/index.md","name":"CVE-2020-5246","record":{"aliases":["GHSA-v955-7g22-2p49"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"GPS Tracking System","requires_auth":"low_privilege","summary":"Attackers can gain admin privileges via LDAP injection in Traccar GPS Tracking System when LDAP is enabled and user names are customizable.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"traccar","vendor":"traccar"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"},{"id":"CWE-90","name":"Improper Neutralization of Special Elements used in an LDAP Query"}],"description":"Traccar GPS Tracking System before version 4.9 has a LDAP injection vulnerability. It occurs when user input is being used in LDAP search filter. By providing specially crafted input, an attacker can modify the logic of the LDAP query and get admin privileges. The issue only impacts instances with LDAP configuration and where users can craft their own names. This has been patched in version 4.9.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"LDAP injection vulnerability in Traccar GPS Tracking System","id":"CVE-2020-5246","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"HTTP Response Splitting in Puma","id":"CVE-2020-5247"},"packages":[],"prev":{"headline":"Remote Code Execution (RCE) vulnerability in dropwizard-validation","id":"CVE-2020-5245"},"products":["Traccar"],"published":"2020-07-14","related":[{"cvss_score":9.7,"headline":"Traccar's unrestricted file upload vulnerability in device image upload could lead to remote code execution","id":"CVE-2024-31214","kev_date_added":null,"published":"2024-04-10"},{"cvss_score":9.5,"headline":"Use of default credentials at Traccar fleet management solution","id":"CVE-2024-7746","kev_date_added":null,"published":"2024-08-13"},{"cvss_score":8.7,"headline":"Traccar Vulnerable to Stored Cross-Site Scripting (XSS) via Malicious SVG File Upload","id":"CVE-2026-25648","kev_date_added":null,"published":"2026-02-23"},{"cvss_score":8.5,"headline":"An unrestricted file upload vulnerability in traccar leads to RCE","id":"CVE-2023-50729","kev_date_added":null,"published":"2024-01-15"},{"cvss_score":7.3,"headline":"Traccar Vulnerable to Authorization Code Theft via Open Redirect in OIDC Provider Endpoints","id":"CVE-2026-25649","kev_date_added":null,"published":"2026-02-23"},{"cvss_score":7.1,"headline":"Traccar Missing Origin Validation in WebSockets","id":"CVE-2025-68930","kev_date_added":null,"published":"2026-02-23"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["Traccar"]},"summary":"Attackers can gain admin privileges via LDAP injection in Traccar GPS Tracking System when LDAP is enabled and user names are customizable.","url":"https://insights.sbomify.com/CVE-2020-5246/"}