{"answers":{"affected":"1 open source package ship an affected version, including tensorflow. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-35958 in the wild and no public exploit code.","fix":"Upgrade tensorflow to 2.5.1 or later.","what":"CVE-2021-35958 is a critical path traversal vulnerability in Google Tensorflow, published on 30 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-35958 and fix it if it is affected.\n\nWhat it is: CVE-2021-35958 is a critical path traversal vulnerability in Google Tensorflow, published on 30 Jun 2021. 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-2021-35958 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- tensorflow (Bitnami): affected all versions; fixed in 2.5.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-2021-35958/ (Markdown: https://insights.sbomify.com/CVE-2021-35958/index.md)","id":"CVE-2021-35958","markdown":"https://insights.sbomify.com/CVE-2021-35958/index.md","name":"CVE-2021-35958","record":{"aliases":["BIT-tensorflow-2021-35958","GHSA-4cm9-63x5-55wm"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"TensorFlow library","requires_auth":"none","summary":"Attackers can overwrite arbitrary files via crafted archives in TensorFlow's get_file utility, though the vendor deems this out of scope for untrusted input.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tensorflow","vendor":"google"}],"cvss":{"score":9.1,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"TensorFlow through 2.5.0 allows attackers to overwrite arbitrary files via a crafted archive when tf.keras.utils.get_file is used with extract=True. NOTE: the vendor's position is that tf.keras.utils.get_file is not intended for untrusted archives","ecosystems":["Bitnami"],"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":"Path traversal in n/a","id":"CVE-2021-35958","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"google:tensorflow","products":["google:tensorflow"],"type":"path_traversal","year":"2021"},"n_packages":1,"n_references":5,"next":{"headline":"Plone has stored XSS in folder contents","id":"CVE-2021-35959"},"packages":[{"ecosystem":"Bitnami","fixed":["2.5.1"],"introduced":["0"],"last_affected":[],"package":"tensorflow","purl":"pkg:bitnami/tensorflow","source":"BIT-tensorflow-2021-35958"}],"prev":{"headline":"Other in n/a","id":"CVE-2021-35957"},"products":["n/a"],"published":"2021-06-30","related":[{"cvss_score":9.8,"headline":"TensorFlow vulnerable to heap out-of-buffer read in the QuantizeAndDequantize operation","id":"CVE-2023-25668","kev_date_added":null,"published":"2023-03-24"},{"cvss_score":9.8,"headline":"Integer Overflow or Wraparound in Google TensorFlow","id":"CVE-2018-7575","kev_date_added":null,"published":"2019-04-24"},{"cvss_score":9.3,"headline":"Arbitrary code execution due to YAML deserialization","id":"CVE-2021-37678","kev_date_added":null,"published":"2021-08-12"},{"cvss_score":9,"headline":"Integer truncation in Shard API usage","id":"CVE-2020-15202","kev_date_added":null,"published":"2020-09-25"},{"cvss_score":9,"headline":"Data leak in Tensorflow","id":"CVE-2020-15205","kev_date_added":null,"published":"2020-09-25"},{"cvss_score":9,"headline":"Denial of Service in Tensorflow","id":"CVE-2020-15206","kev_date_added":null,"published":"2020-09-25"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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":["n/a"]},"summary":"Attackers can overwrite arbitrary files via crafted archives in TensorFlow's get_file utility, though the vendor deems this out of scope for untrusted input.","url":"https://insights.sbomify.com/CVE-2021-35958/"}