{"answers":{"affected":"2 open source packages ship an affected version, including fastify-csrf. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-28482 in the wild and no public exploit code.","fix":"Upgrade fastify-csrf to 3.0.0 or later.","what":"CVE-2020-28482 is a medium-severity vulnerability in fastify-csrf, published on 19 Jan 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-28482 and fix it if it is affected.\n\nWhat it is: CVE-2020-28482 is a medium-severity vulnerability in fastify-csrf, published on 19 Jan 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-28482 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- fastify-csrf (npm): affected all versions; fixed in 3.0.0\n- fastify-csrf (npm): affected all versions; fixed in 3.0.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-28482/ (Markdown: https://insights.sbomify.com/CVE-2020-28482/index.md)","id":"CVE-2020-28482","markdown":"https://insights.sbomify.com/CVE-2020-28482/index.md","name":"CVE-2020-28482","record":{"aliases":["GHSA-49wp-qq6x-g2rf","SNYK-JS-FASTIFYCSRF-1062044"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Fastify CSRF library","requires_auth":"none","summary":"Insecure cookie defaults and token exposure in GET parameters allow attackers to bypass CSRF protections in applications using this library.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"fastify-csrf","vendor":"fastify"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"This affects the package fastify-csrf before 3.0.0. 1. The generated cookie used insecure defaults, and did not have the httpOnly flag on: cookieOpts: { path: '/', sameSite: true } 2. The CSRF token was available in the GET query parameter","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":"Cross-site Request Forgery (CSRF)","id":"CVE-2020-28482","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"csrf","year":"2020"},"n_packages":2,"n_references":2,"next":{"headline":"HTTP Response Splitting","id":"CVE-2020-28483"},"packages":[{"ecosystem":"npm","fixed":["3.0.0"],"introduced":["0"],"last_affected":[],"package":"fastify-csrf","purl":null,"source":"GHSA-49wp-qq6x-g2rf"},{"ecosystem":"npm","fixed":["3.0.0"],"introduced":["0"],"last_affected":[],"package":"fastify-csrf","purl":"pkg:npm/fastify-csrf","source":"GHSA-49wp-qq6x-g2rf"}],"prev":{"headline":"Insecure Defaults","id":"CVE-2020-28481"},"products":["fastify-csrf"],"published":"2021-01-19","related":[{"cvss_score":6.5,"headline":"Lack of protection against cookie tossing attacks in fastify-csrf","id":"CVE-2021-29624","kev_date_added":null,"published":"2021-05-19"}],"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":"Insecure cookie defaults and token exposure in GET parameters allow attackers to bypass CSRF protections in applications using this library.","url":"https://insights.sbomify.com/CVE-2020-28482/"}