# CVE-2024-39001: ag-grid packages vulnerable to Prototype Pollution > Prototype pollution in ag-grid-enterprise allows attackers to execute arbitrary code or cause denial of service via property injection. - **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 1 Jul 2024 - **Updated:** 2 Aug 2024 - **Also known as:** GHSA-328p-362g-r48j ## What is CVE-2024-39001? CVE-2024-39001 is a medium-severity code injection vulnerability in n/a, published on 1 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description ag-grid-enterprise v31.3.2 was discovered to contain a prototype pollution via the component _ModuleSupport.jsonApply. This vulnerability allows attackers to execute arbitrary code or cause a Denial of Service (DoS) via injecting arbitrary properties. Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes) ## Which versions are affected by CVE-2024-39001? 12 open source packages ship an affected version, including @ag-grid-enterprise/charts, ag-grid-community and ag-grid-enterprise. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `@ag-grid-enterprise/charts` | npm | All versions | 31.3.4 | | `@ag-grid-enterprise/charts` | npm | All versions | 31.3.4 | | `@ag-grid-enterprise/charts` | npm | From 32.0.0 | 32.0.1 | | `@ag-grid-enterprise/charts` | npm | From 32.0.0 | 32.0.1 | | `ag-grid-community` | npm | All versions | 31.3.4 | | `ag-grid-community` | npm | All versions | 31.3.4 | | `ag-grid-community` | npm | From 32.0.0 | 32.0.1 | | `ag-grid-community` | npm | From 32.0.0 | 32.0.1 | | `ag-grid-enterprise` | npm | All versions | 31.3.4 | | `ag-grid-enterprise` | npm | All versions | 31.3.4 | | `ag-grid-enterprise` | npm | From 32.0.0 | 32.0.1 | | `ag-grid-enterprise` | npm | From 32.0.0 | 32.0.1 | Products: Ag-Grid Ag-Grid, Ag-Grid Ag Charts. ## How do I fix CVE-2024-39001? Upgrade @ag-grid-enterprise/charts to a fixed version for your release line: 31.3.4 or 32.0.1. ## Is CVE-2024-39001 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-39001 exists. ## Other vulnerabilities in n/a - [CVE-2024-38996](https://insights.sbomify.com/CVE-2024-38996/): Prototype pollution in ag-grid-community via the _.mergeDeep function (critical 9.8) - [CVE-2017-16009](https://insights.sbomify.com/CVE-2017-16009/): XSS via Angular Expression in ag-grid (medium 6.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-39001 and fix it if it is affected. What it is: CVE-2024-39001 is a medium-severity code injection vulnerability in n/a, published on 1 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-39001 exists. Affected packages and fixed versions: - @ag-grid-enterprise/charts (npm): affected all versions; fixed in 31.3.4 - @ag-grid-enterprise/charts (npm): affected all versions; fixed in 31.3.4 - @ag-grid-enterprise/charts (npm): affected from 32.0.0; fixed in 32.0.1 - @ag-grid-enterprise/charts (npm): affected from 32.0.0; fixed in 32.0.1 - ag-grid-community (npm): affected all versions; fixed in 31.3.4 - ag-grid-community (npm): affected all versions; fixed in 31.3.4 - ag-grid-community (npm): affected from 32.0.0; fixed in 32.0.1 - ag-grid-community (npm): affected from 32.0.0; fixed in 32.0.1 - ag-grid-enterprise (npm): affected all versions; fixed in 31.3.4 - ag-grid-enterprise (npm): affected all versions; fixed in 31.3.4 - ag-grid-enterprise (npm): affected from 32.0.0; fixed in 32.0.1 - ag-grid-enterprise (npm): affected from 32.0.0; fixed in 32.0.1 Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-39001/ (Markdown: https://insights.sbomify.com/CVE-2024-39001/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-39001 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-39001 - OSV: https://osv.dev/vulnerability/CVE-2024-39001 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-39001/ Summaries are generated and may contain mistakes; the official description above is the record.