# CVE-2022-35912: Grails framework Remote Code Execution via Data Binding

> Remote attackers can execute arbitrary code via data binding in Grails when specific Java 8 configurations are active.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-6rh6-x8ww-9h97

## What is CVE-2022-35912?

CVE-2022-35912 is a critical code injection vulnerability in n/a, published on 19 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In grails-databinding in Grails before 3.3.15, 4.x before 4.1.1, 5.x before 5.1.9, and 5.2.x before 5.2.1 (at least when certain Java 8 configurations are used), data binding allows a remote attacker to execute code by gaining access to the class loader.

## Which versions are affected by CVE-2022-35912?

8 open source packages ship an affected version, including org.grails:grails-databinding. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.grails:grails-databinding` | Maven | From 3.3.10 | 3.3.15 |
| `org.grails:grails-databinding` | Maven | From 3.3.10 | 3.3.15 |
| `org.grails:grails-databinding` | Maven | From 4.0.0 | 4.1.1 |
| `org.grails:grails-databinding` | Maven | From 4.0.0 | 4.1.1 |
| `org.grails:grails-databinding` | Maven | From 5.0.0 | 5.1.9 |
| `org.grails:grails-databinding` | Maven | From 5.0.0 | 5.1.9 |
| `org.grails:grails-databinding` | Maven | From 5.2.0 | 5.2.1 |
| `org.grails:grails-databinding` | Maven | From 5.2.0 | 5.2.1 |

Products: Grails Grails.

## How do I fix CVE-2022-35912?

Upgrade org.grails:grails-databinding to a fixed version for your release line: 3.3.15, 4.1.1, 5.1.9 or 5.2.1.

## Is CVE-2022-35912 being exploited?

There is no known exploitation of CVE-2022-35912 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2019-12728](https://insights.sbomify.com/CVE-2019-12728/): Incorrect Resource Transfer Between Spheres in Grails (high 8.1)
- [CVE-2023-46131](https://insights.sbomify.com/CVE-2023-46131/): Grails® data binding causes JVM crash and/or DoS (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-35912 and fix it if it is affected.

What it is: CVE-2022-35912 is a critical code injection vulnerability in n/a, published on 19 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-35912 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.grails:grails-databinding (Maven): affected from 3.3.10; fixed in 3.3.15
- org.grails:grails-databinding (Maven): affected from 3.3.10; fixed in 3.3.15
- org.grails:grails-databinding (Maven): affected from 4.0.0; fixed in 4.1.1
- org.grails:grails-databinding (Maven): affected from 4.0.0; fixed in 4.1.1
- org.grails:grails-databinding (Maven): affected from 5.0.0; fixed in 5.1.9
- org.grails:grails-databinding (Maven): affected from 5.0.0; fixed in 5.1.9
- org.grails:grails-databinding (Maven): affected from 5.2.0; fixed in 5.2.1
- org.grails:grails-databinding (Maven): affected from 5.2.0; fixed in 5.2.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-2022-35912/ (Markdown: https://insights.sbomify.com/CVE-2022-35912/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-35912
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-35912
- OSV: https://osv.dev/vulnerability/CVE-2022-35912

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-35912/
Summaries are generated and may contain mistakes; the official description above is the record.