Vulnerability in org.grails:grails-databinding (CVE-2022-35912)

Summary

Vulnerability in org.grails:grails-databinding (CVE-2022-35912). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 5.2.1 or later.

Original description

The description as published by the source.

Impact

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.

Patches

Grails framework versions 5.2.1, 5.1.9, 4.1.1, and 3.3.15

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:

Credit

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

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2022-35912 has been found in org.grails:grails-databinding.
Successful exploitation can lead to full system takeover.
What to do: upgrade org.grails:grails-databinding to 5.2.1 or later.
If unsure, ask your IT team or search "org.grails:grails-databinding CVE-2022-35912" on the vendor's site.

CVE-2022-35912 (org.grails:grails-databinding)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 5.2.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in org.grails:grails-databinding.

📍 Affected scope

Check the vendor advisory for the affected versions of org.grails:grails-databinding.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 5.2.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで org.grails:grails-databinding を使っているサービスとバージョンを洗い出す。
2
Apply patch patch
```
Upgrade org.grails:grails-databinding to 5.2.1
```
ステージング環境で 5.2.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Maven org.grails:grails-databinding

[{"type":"ECOSYSTEM","events":[{"introduced":"5.2.0"},{"fixed":"5.2.1"}]}]

References

advisory nvd.nist.gov
package github.com
web github.com
web github.com
web grails.org
web openwall.com