{"answers":{"affected":"3 open source packages ship an affected version, including radicale and Radicale. It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-1505 in the wild and no public exploit code.","fix":"Upgrade radicale to 1.1 or later.","what":"CVE-2016-1505 is a critical path traversal vulnerability in n/a, published on 3 Feb 2016. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-1505 and fix it if it is affected.\n\nWhat it is: CVE-2016-1505 is a critical path traversal vulnerability in n/a, published on 3 Feb 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2016-1505 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- radicale (PyPI): affected all versions; fixed in 1.1\n- radicale (PyPI): affected all versions; fixed in 1.1\n- Radicale (PyPI): affected all versions; fixed in 1.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-2016-1505/ (Markdown: https://insights.sbomify.com/CVE-2016-1505/index.md)","id":"CVE-2016-1505","markdown":"https://insights.sbomify.com/CVE-2016-1505/index.md","name":"CVE-2016-1505","record":{"aliases":["GHSA-84cw-mxhv-qvv4","PYSEC-2026-512"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Radicale CalDAV server","requires_auth":"none","summary":"Remote attackers can read or write arbitrary files on Windows systems via crafted paths in the Radicale filesystem storage backend.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"radicale","vendor":"radicale"}],"cvss":{"score":10,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-21","name":null}],"description":"The filesystem storage backend in Radicale before 1.1 on Windows allows remote attackers to read or write to arbitrary files via a crafted path, as demonstrated by /c:/file/ignore.","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":"Radicale is vulnerable to directory traversal on Windows Filesystem Storage Backend component","id":"CVE-2016-1505","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2016"},"n_packages":3,"n_references":7,"next":{"headline":"Memory corruption in n/a","id":"CVE-2016-1513"},"packages":[{"ecosystem":"PyPI","fixed":["1.1"],"introduced":["0"],"last_affected":[],"package":"Radicale","purl":null,"source":"GHSA-84cw-mxhv-qvv4"},{"ecosystem":"PyPI","fixed":["1.1"],"introduced":["0"],"last_affected":[],"package":"radicale","purl":"pkg:pypi/radicale","source":"GHSA-84cw-mxhv-qvv4"},{"ecosystem":"PyPI","fixed":["1.1"],"introduced":["0"],"last_affected":[],"package":"radicale","purl":"pkg:pypi/radicale","source":"PYSEC-2026-512"}],"prev":{"headline":"dhcpcd before 6.10.0 allows remote attackers to cause a denial of service (invalid read and crash) via vectors related to the option length.","id":"CVE-2016-1504"},"products":["n/a"],"published":"2016-02-03","related":[{"cvss_score":10,"headline":"Radicale vulnerable to arbitrary file read or write","id":"CVE-2015-8747","kev_date_added":null,"published":"2016-02-03"},{"cvss_score":8.1,"headline":"Radicale is vulnerable to timing oracles and simple bruteforce attacks","id":"CVE-2017-8342","kev_date_added":null,"published":"2017-04-30"},{"cvss_score":5.3,"headline":"Radicale regex metacharacters injection in the user name","id":"CVE-2015-8748","kev_date_added":null,"published":"2016-02-03"}],"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-05","vendors":["n/a"]},"summary":"Remote attackers can read or write arbitrary files on Windows systems via crafted paths in the Radicale filesystem storage backend.","url":"https://insights.sbomify.com/CVE-2016-1505/"}