CVE-2022-35912

Grails framework Remote Code Execution via Data Binding

References

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35912
https://grails.org/blog/2022-07-18-rce-vulnerability.html

For more information

If you have any questions or comments about this advisory:

• https://grails.org/blog/2022-07-18-rce-vulnerability.html
• https://github.com/grails/grails-core/issues/12626
• Email us at [email protected]

Credit

This vulnerability was discovered by meizjm3i and codeplutos of AntGroup FG Security Lab

A vulnerability has been discovered in the Grails data-binding logic which allows for Remote Code Execution in a Grails application. This exploit requires the application to be running on Java 8, either deployed as a WAR to a servlet container, or an executable JAR.

CVE-2022-35912 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.3.15, 4.1.1, 5.1.9, 5.2.1); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Grails framework versions 5.2.1, 5.1.9, 4.1.1, and 3.3.15

1. What is CVE-2022-35912? CVE-2022-35912 is a critical-severity security vulnerability in org.grails:grails-databinding (maven), affecting versions >= 3.3.10, < 3.3.15. It is fixed in 3.3.15, 4.1.1, 5.1.9, 5.2.1.
2. How severe is CVE-2022-35912? CVE-2022-35912 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.grails:grails-databinding are affected by CVE-2022-35912? org.grails:grails-databinding (maven) versions >= 3.3.10, < 3.3.15 is affected.
4. Is there a fix for CVE-2022-35912? Yes. CVE-2022-35912 is fixed in 3.3.15, 4.1.1, 5.1.9, 5.2.1. Upgrade to this version or later.
5. Is CVE-2022-35912 exploitable, and should I be worried? Whether CVE-2022-35912 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-35912 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-35912?
   • Upgrade org.grails:grails-databinding to 3.3.15 or later
   • Upgrade org.grails:grails-databinding to 4.1.1 or later
   • Upgrade org.grails:grails-databinding to 5.1.9 or later
   • Upgrade org.grails:grails-databinding to 5.2.1 or later

Other vulnerabilities in org.grails:grails-databinding