{"answers":{"affected":"2 open source packages ship an affected version, including react-native-fast-image. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-7696 in the wild and no public exploit code.","fix":"Upgrade react-native-fast-image to 8.3.0 or later.","what":"CVE-2020-7696 is a medium-severity vulnerability in react-native-fast-image, published on 17 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-7696 and fix it if it is affected.\n\nWhat it is: CVE-2020-7696 is a medium-severity vulnerability in react-native-fast-image, published on 17 Jul 2020. 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-2020-7696 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- react-native-fast-image (npm): affected all versions; fixed in 8.3.0\n- react-native-fast-image (npm): affected all versions; fixed in 8.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-2020-7696/ (Markdown: https://insights.sbomify.com/CVE-2020-7696/index.md)","id":"CVE-2020-7696","markdown":"https://insights.sbomify.com/CVE-2020-7696/index.md","name":"CVE-2020-7696","record":{"aliases":["GHSA-6xhg-q9c8-rj32"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"React Native image library","requires_auth":"none","summary":"An attacker can leak sensitive headers like authorization tokens to unintended servers due to header persistence in react-native-fast-image.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"react-native-fast-image","vendor":"react-native-fast-image_project"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"This affects all versions of package react-native-fast-image. When an image with source={{uri: \"...\", headers: { host: \"somehost.com\", authorization: \"...\" }} is loaded, all other subsequent images will use the same headers, this can lead to signing credentials or other session tokens being leaked to other servers.","ecosystems":["npm"],"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":"Information Exposure","id":"CVE-2020-7696","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":2,"n_references":3,"next":{"headline":"Command Injection","id":"CVE-2020-7697"},"packages":[{"ecosystem":"npm","fixed":["8.3.0"],"introduced":["0"],"last_affected":[],"package":"react-native-fast-image","purl":null,"source":"GHSA-6xhg-q9c8-rj32"},{"ecosystem":"npm","fixed":["8.3.0"],"introduced":["0"],"last_affected":[],"package":"react-native-fast-image","purl":"pkg:npm/react-native-fast-image","source":"GHSA-6xhg-q9c8-rj32"}],"prev":{"headline":"HTTP Response Splitting","id":"CVE-2020-7695"},"products":["react-native-fast-image"],"published":"2020-07-17","related":[],"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":["n/a"]},"summary":"An attacker can leak sensitive headers like authorization tokens to unintended servers due to header persistence in react-native-fast-image.","url":"https://insights.sbomify.com/CVE-2020-7696/"}