← Back
CVE-2022-25647
high
CVSS 7.7
Unsafe Deserialization in com.google.code.gson:gson (CVE-2022-25647)
Summary
vulnerability in com.google.code.gson:gson (CVE-2022-25647). Data can be tampered with by attackers. Mitigation: upgrade to `2.8.9` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2022-25647** has been found in com.google.code.gson:gson.
Data can be tampered with by attackers. CVSS score: 7.7/10.
What to do: upgrade com.google.code.gson:gson to **2.8.9** or later.
If unsure, ask your IT team or search "com.google.code.gson:gson CVE-2022-25647" on the vendor's site.
CVE-2022-25647 (com.google.code.gson:gson) — CWE-502 / CVSS v3 7.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `2.8.9` — 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
**unsafe deserialization** (CWE-502) exists in com.google.code.gson:gson.
📍 Affected scope
com.google.code.gson:gson — .
🔥 Severity
Severity: High (CVSS 7.7/10). Data can be tampered with by attackers
🔧 How to fix
Update to **2.8.9**.
🛡️ 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. Run `grep -r 'com.google.code.gson:gson' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'com.google.code.gson:gson' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `com.google.code.gson:gson` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade com.google.code.gson:gson to 2.8.9ステージング環境で 2.8.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
com.google.code.gson:gson
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.8.9"}]}]
References
- advisory af854a3a-2127-422b-91ae-364da2661108
- advisory https://nvd.nist.gov/vuln/detail/CVE-2022-25647
- package https://github.com/google/gson
- web https://github.com/google/gson/pull/1991
- web https://github.com/google/gson/pull/1991/commits
- web https://lists.debian.org/debian-lts-announce/2022/05/msg00015.html
- web https://lists.debian.org/debian-lts-announce/2022/09/msg00009.html
- web https://snyk.io/vuln/SNYK-JAVA-COMGOOGLECODEGSON-1730327
- web https://www.debian.org/security/2022/dsa-5227
- web https://www.oracle.com/security-alerts/cpujul2022.html
- web https://security.netapp.com/advisory/ntap-20220901-0009
- web https://github.com/advisories/GHSA-4jrv-ppp4-jm57