{"answers":{"affected":"2 open source packages ship an affected version, including next. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-5284 exists.","fix":"Upgrade next to 9.3.2 or later.","what":"CVE-2020-5284 is a medium-severity path traversal vulnerability in zeit next.js, published on 30 Mar 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-5284 and fix it if it is affected.\n\nWhat it is: CVE-2020-5284 is a medium-severity path traversal vulnerability in zeit next.js, published on 30 Mar 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-5284 exists.\n\nAffected packages and fixed versions:\n- next (npm): affected from 0.9.9; fixed in 9.3.2\n- next (npm): affected from 0.9.9; fixed in 9.3.2\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-5284/ (Markdown: https://insights.sbomify.com/CVE-2020-5284/index.md)","id":"CVE-2020-5284","markdown":"https://insights.sbomify.com/CVE-2020-5284/index.md","name":"CVE-2020-5284","record":{"aliases":["GHSA-fq77-7p7r-83rj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Next.js framework","requires_auth":"low_privilege","summary":"Attackers can access files in the dist directory via crafted requests, potentially exposing build assets or sensitive data stored there.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"next.js","vendor":"zeit"}],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"},{"id":"CWE-23","name":"Relative Path Traversal"}],"description":"Next.js versions before 9.3.2 have a directory traversal vulnerability. Attackers could craft special requests to access files in the dist directory (.next). This does not affect files outside of the dist directory (.next). In general, the dist directory only holds build assets unless your application intentionally stores other assets under this directory. This issue is fixed in version 9.3.2.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2020/CVE-2020-5284.yaml","stars":null,"title":"Next.js \u003c9.3.2 - Local File Inclusion"}],"tier":"weaponised"},"has_fix":true,"headline":"Directory Traversal in Next.js versions below 9.3.2","id":"CVE-2020-5284","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"path_traversal","year":"2020"},"n_packages":2,"n_references":2,"next":{"headline":"Reflected XSS with back parameter in PrestaShop","id":"CVE-2020-5285"},"packages":[{"ecosystem":"npm","fixed":["9.3.2"],"introduced":["0.9.9"],"last_affected":[],"package":"next","purl":null,"source":"GHSA-fq77-7p7r-83rj"},{"ecosystem":"npm","fixed":["9.3.2"],"introduced":["0.9.9"],"last_affected":[],"package":"next","purl":"pkg:npm/next","source":"GHSA-fq77-7p7r-83rj"}],"prev":{"headline":"XSS vulnerability in CVS show_subdir_lastmod support","id":"CVE-2020-5283"},"products":["next.js"],"published":"2020-03-30","related":[{"cvss_score":7.5,"headline":"Directory traversal vulnerability in Next.js","id":"CVE-2018-6184","kev_date_added":null,"published":"2018-01-24"},{"cvss_score":7.5,"headline":"Next.js Directory Traversal Vulnerability","id":"CVE-2017-16877","kev_date_added":null,"published":"2017-11-17"},{"cvss_score":6.1,"headline":"Next.js has cross site scripting (XSS) vulnerability via the 404 or 500 /_error page","id":"CVE-2018-18282","kev_date_added":null,"published":"2018-10-12"}],"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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["zeit"]},"summary":"Attackers can access files in the dist directory via crafted requests, potentially exposing build assets or sensitive data stored there.","url":"https://insights.sbomify.com/CVE-2020-5284/"}