{"answers":{"affected":"1 open source package ship an affected version, including tensorflow. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-35938 in the wild and no public exploit code.","fix":"Upgrade tensorflow to a fixed version for your release line: 2.7.2, 2.8.1 or 2.9.1.","what":"CVE-2022-35938 is a high-severity memory corruption vulnerability in Google Tensorflow, published on 16 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-35938 and fix it if it is affected.\n\nWhat it is: CVE-2022-35938 is a high-severity memory corruption vulnerability in Google Tensorflow, published on 16 Sep 2022. 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-2022-35938 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- tensorflow (Bitnami): affected from 2.7.0; fixed in 2.7.2, 2.8.1, 2.9.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-2022-35938/ (Markdown: https://insights.sbomify.com/CVE-2022-35938/index.md)","id":"CVE-2022-35938","markdown":"https://insights.sbomify.com/CVE-2022-35938/index.md","name":"CVE-2022-35938","record":{"aliases":["BIT-tensorflow-2022-35938","GHSA-3m3g-pf5v-5hpj"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"TensorFlow Lite Micro","requires_auth":"none","summary":"An out-of-bounds read in TensorFlow Lite Micro's Gather_nd operation allows attackers to cause crashes or read sensitive memory.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"tensorflow","vendor":"google"}],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"TensorFlow is an open source platform for machine learning. The `GatherNd` function takes arguments that determine the sizes of inputs and outputs. If the inputs given are greater than or equal to the sizes of the outputs, an out-of-bounds memory read or a crash is triggered. This issue has been patched in GitHub commit 4142e47e9e31db481781b955ed3ff807a781b494. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue.","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":"OOB read in `Gather_nd` op in TensorFlow Lite Micro","id":"CVE-2022-35938","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"google:tensorflow","products":["google:tensorflow"],"type":"memory_corruption","year":"2022"},"n_packages":1,"n_references":3,"next":{"headline":"Out of bounds write in `scatter_nd` op in TensorFlow Lite","id":"CVE-2022-35939"},"packages":[{"ecosystem":"Bitnami","fixed":["2.7.2","2.8.1","2.9.1"],"introduced":["2.7.0","2.8.0","2.9.0"],"last_affected":[],"package":"tensorflow","purl":"pkg:bitnami/tensorflow","source":"BIT-tensorflow-2022-35938"}],"prev":{"headline":"OOB read in `Gather_nd` op in TensorFlow Lite","id":"CVE-2022-35937"},"products":["tensorflow"],"published":"2022-09-16","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.1,"headline":"Path traversal in n/a","id":"CVE-2021-35958","kev_date_added":null,"published":"2021-06-30"},{"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["tensorflow"]},"summary":"An out-of-bounds read in TensorFlow Lite Micro's Gather_nd operation allows attackers to cause crashes or read sensitive memory.","url":"https://insights.sbomify.com/CVE-2022-35938/"}