{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-36065 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-36065 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-36065 is a high-severity vulnerability in growthbook, published on 6 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-36065 and fix it if it is affected.\n\nWhat it is: CVE-2022-36065 is a high-severity vulnerability in growthbook, published on 6 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-36065 in the wild and no public exploit code.\n\nAffected product: growthbook. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-36065/ (Markdown: https://insights.sbomify.com/CVE-2022-36065/index.md)","id":"CVE-2022-36065","markdown":"https://insights.sbomify.com/CVE-2022-36065/index.md","name":"CVE-2022-36065","record":{"aliases":["GHSA-j24q-55xh-wm4r"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"GrowthBook feature flagging","requires_auth":"low_privilege","summary":"Attackers can upload malicious files to execute code in self-hosted GrowthBook instances with weak JWT secrets and local storage.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"growthbook","vendor":"growthbook"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-24","name":"Path Traversal: '../filedir'"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"GrowthBook is an open-source platform for feature flagging and A/B testing. With some self-hosted configurations in versions prior to 2022-08-29, attackers can register new accounts and upload files to arbitrary directories within the container. If the attacker uploads a Python script to the right location, they can execute arbitrary code within the container. To be affected, ALL of the following must be true: Self-hosted deployment (GrowthBook Cloud is unaffected); using local file uploads (as opposed to S3 or Google Cloud Storage); NODE_ENV set to a non-production value and JWT_SECRET set to an easily guessable string like `dev`. This issue is patched in commit 1a5edff8786d141161bf880c2fd9ccbe2850a264 (2022-08-29). As a workaround, set `JWT_SECRET` environment variable to a long random string. This will stop arbitrary file uploads, but the only way to stop attackers from registering accounts is by updating to the latest build.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"GrowthBook account creation and file upload vulnerability in self-hosted configurations","id":"CVE-2022-36065","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Discourse vulnerable to RCE via admins uploading maliciously zipped file","id":"CVE-2022-36066"},"packages":[],"prev":{"headline":"Shescape Inefficient Regular Expression Complexity vulnerability","id":"CVE-2022-36064"},"products":["growthbook"],"published":"2022-09-06","related":[],"sources":[{"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":"total"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["growthbook"]},"summary":"Attackers can upload malicious files to execute code in self-hosted GrowthBook instances with weak JWT secrets and local storage.","url":"https://insights.sbomify.com/CVE-2022-36065/"}