{"answers":{"affected":"1 open source package ship an affected version, including grpcio. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-8359 in the wild and no public exploit code.","fix":"Upgrade grpcio to 1.3.0 or later.","what":"CVE-2017-8359 is a critical use after free vulnerability in n/a, published on 30 Apr 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-8359 and fix it if it is affected.\n\nWhat it is: CVE-2017-8359 is a critical use after free vulnerability in n/a, published on 30 Apr 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-8359 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- grpcio (PyPI): affected all versions; fixed in 1.3.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-8359/ (Markdown: https://insights.sbomify.com/CVE-2017-8359/index.md)","id":"CVE-2017-8359","markdown":"https://insights.sbomify.com/CVE-2017-8359/index.md","name":"CVE-2017-8359","record":{"aliases":["DEBIAN-CVE-2017-8359","GHSA-j2fw-rfr9-pfrh","PYSEC-2017-101","UBUNTU-CVE-2017-8359"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"gRPC library","requires_auth":"none","summary":"An out-of-bounds write via use-after-free in gRPC allows attackers to execute arbitrary code or cause denial of service.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"grpc","vendor":"grpc"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"Google gRPC before 2017-03-29 has an out-of-bounds write caused by a heap-based use-after-free related to the grpc_call_destroy function in core/lib/surface/call.c.","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":"Use after free in n/a","id":"CVE-2017-8359","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"use_after_free","year":"2017"},"n_packages":1,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2017-8360"},"packages":[{"ecosystem":"PyPI","fixed":["1.3.0"],"introduced":["0"],"last_affected":[],"package":"grpcio","purl":"pkg:pypi/grpcio","source":"PYSEC-2017-101"}],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2017-8358"},"products":["n/a"],"published":"2017-04-30","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-9431","kev_date_added":null,"published":"2017-06-05"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-7860","kev_date_added":null,"published":"2017-04-14"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-7861","kev_date_added":null,"published":"2017-04-14"},{"cvss_score":9.1,"headline":"gRPC-Go has an authorization bypass via missing leading slash in :path","id":"CVE-2026-33186","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":7.5,"headline":"Denial of Service in gRPC Core","id":"CVE-2023-4785","kev_date_added":null,"published":"2023-09-13"},{"cvss_score":7.5,"headline":"Denial-of-Service in gRPC","id":"CVE-2023-33953","kev_date_added":null,"published":"2023-08-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"An out-of-bounds write via use-after-free in gRPC allows attackers to execute arbitrary code or cause denial of service.","url":"https://insights.sbomify.com/CVE-2017-8359/"}