{"answers":{"affected":"4 open source packages ship an affected version, including trytond and tryton. It affects 1 product.","exploited":"There is no known exploitation of CVE-2013-4510 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2013-4510 is a high-severity path traversal vulnerability in n/a, published on 15 Nov 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2013-4510 and fix it if it is affected.\n\nWhat it is: CVE-2013-4510 is a high-severity path traversal vulnerability in n/a, published on 15 Nov 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2013-4510 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- trytond (PyPI): affected all versions; no fix listed\n- trytond (PyPI): affected all versions; no fix listed\n- trytond (PyPI): affected all versions; no fix listed\n- tryton (PyPI): affected all versions; fixed in 3.0.1\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-2013-4510/ (Markdown: https://insights.sbomify.com/CVE-2013-4510/index.md)","id":"CVE-2013-4510","markdown":"https://insights.sbomify.com/CVE-2013-4510/index.md","name":"CVE-2013-4510","record":{"aliases":["DEBIAN-CVE-2013-4510","DSA-2791-1","GHSA-qjmc-wwmw-cq9r","PYSEC-2013-28","PYSEC-2026-1054"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Tryton client","requires_auth":"none","summary":"A remote server can write arbitrary files to the Tryton client via path traversal in report extensions, requiring user interaction to connect.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"tryton","vendor":"tryton"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:C/A:N","version":"2.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Directory traversal vulnerability in the client in Tryton 3.0.0, as distributed before 20131104 and earlier, allows remote servers to write arbitrary files via path separators in the extension of a report.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Tryton Directory Traversal vulnerability","id":"CVE-2013-4510","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2013"},"n_packages":4,"n_references":5,"next":{"headline":"Integer overflow in n/a","id":"CVE-2013-4511"},"packages":[{"ecosystem":"PyPI","fixed":["3.0.1"],"introduced":["0"],"last_affected":[],"package":"tryton","purl":"pkg:pypi/tryton","source":"PYSEC-2013-28"},{"ecosystem":"PyPI","fixed":[],"introduced":[],"last_affected":[],"package":"trytond","purl":null,"source":"GHSA-qjmc-wwmw-cq9r"},{"ecosystem":"PyPI","fixed":[],"introduced":[],"last_affected":[],"package":"trytond","purl":"pkg:pypi/trytond","source":"GHSA-qjmc-wwmw-cq9r"},{"ecosystem":"PyPI","fixed":[],"introduced":[],"last_affected":[],"package":"trytond","purl":"pkg:pypi/trytond","source":"PYSEC-2026-1054"}],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2013-4509"},"products":["n/a"],"published":"2013-11-15","related":[{"cvss_score":8.8,"headline":"Tryton vulnerable to arbitrary command execution","id":"CVE-2014-6633","kev_date_added":null,"published":"2018-04-12"},{"cvss_score":5.9,"headline":"Session Fixation in Tryton","id":"CVE-2018-19443","kev_date_added":null,"published":"2018-11-22"},{"cvss_score":5.3,"headline":"Tryton Information Disclosure Vulnerability","id":"CVE-2017-0360","kev_date_added":null,"published":"2017-04-04"},{"cvss_score":5.3,"headline":"Tryton allows users to read the hashed password","id":"CVE-2016-1241","kev_date_added":null,"published":"2016-09-07"},{"cvss_score":4.4,"headline":"Tryton allow authenticated users with certain permissions to read arbitrary files via the name parameter","id":"CVE-2016-1242","kev_date_added":null,"published":"2016-09-07"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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-06","vendors":["n/a"]},"summary":"A remote server can write arbitrary files to the Tryton client via path traversal in report extensions, requiring user interaction to connect.","url":"https://insights.sbomify.com/CVE-2013-4510/"}