CVE-2022-36065
Summary
| CVE | CVE-2022-36065 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2022-09-06 21:15:00 UTC |
| Updated | 2023-07-21 20:52:00 UTC |
| 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. |
Risk And Classification
Problem Types: CWE-22
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Growthbook | Growthbook | All | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Secure file uploads when NODE_ENV=dev by jdorn · Pull Request #487 · growthbook/growthbook · GitHub | MISC | github.com | |
| Account creation and file upload vulnerability in self-hosted GrowthBook · Advisory · growthbook/growthbook · GitHub | CONFIRM | github.com | |
| Secure file uploads when NODE_ENV=dev (#487) · growthbook/growthbook@1a5edff · GitHub | MISC | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.