{"answers":{"affected":"2 open source packages ship an affected version, including koji. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-1002153 in the wild and no public exploit code.","fix":"Upgrade koji to 1.15.0 or later.","what":"CVE-2017-1002153 is a high-severity path traversal vulnerability in Koji, published on 6 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-1002153 and fix it if it is affected.\n\nWhat it is: CVE-2017-1002153 is a high-severity path traversal vulnerability in Koji, published on 6 Oct 2017. 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-2017-1002153 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- koji (PyPI): affected all versions; fixed in 1.15.0\n- koji (PyPI): affected all versions; fixed in 1.15.0\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-2017-1002153/ (Markdown: https://insights.sbomify.com/CVE-2017-1002153/index.md)","id":"CVE-2017-1002153","markdown":"https://insights.sbomify.com/CVE-2017-1002153/index.md","name":"CVE-2017-1002153","record":{"aliases":["GHSA-vwp5-w4rq-g4cc","UBUNTU-CVE-2017-1002153"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Koji build system","requires_auth":"none","summary":"Attackers can bypass blacklisted SCM paths in Koji to submit unauthorized builds, compromising build integrity.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fedora","cpe":[{"product":"koji","vendor":"koji_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Koji 1.13.0 does not properly validate SCM paths, allowing an attacker to work around blacklisted paths for build submission.","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":"Koji blacklisted paths workaround","id":"CVE-2017-1002153","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2017"},"n_packages":2,"n_references":1,"next":{"headline":"modulemd uses an unsafe function for processing externally provided data","id":"CVE-2017-1002157"},"packages":[{"ecosystem":"PyPI","fixed":["1.15.0"],"introduced":["0"],"last_affected":[],"package":"koji","purl":null,"source":"GHSA-vwp5-w4rq-g4cc"},{"ecosystem":"PyPI","fixed":["1.15.0"],"introduced":["0"],"last_affected":[],"package":"koji","purl":"pkg:pypi/koji","source":"GHSA-vwp5-w4rq-g4cc"}],"prev":{"headline":"Bodhi Cross-site Scripting Vulnerability","id":"CVE-2017-1002152"},"products":["Koji"],"published":"2017-10-06","related":[{"cvss_score":9.1,"headline":"Koji hub call does not perform correct access checks","id":"CVE-2018-1002150","kev_date_added":null,"published":"2018-04-04"},{"cvss_score":6.5,"headline":"koji hub allows arbitrary upload destinations","id":"CVE-2019-17109","kev_date_added":null,"published":"2019-10-09"}],"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":"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-09-16","vendors":["Koji Project"]},"summary":"Attackers can bypass blacklisted SCM paths in Koji to submit unauthorized builds, compromising build integrity.","url":"https://insights.sbomify.com/CVE-2017-1002153/"}