# CVE-2022-25845: Deserialization of Untrusted Data

> Attackers can execute arbitrary code on remote servers by bypassing autoType restrictions in the fastjson library.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jun 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-pv7h-hx5h-mgfj, SNYK-JAVA-COMALIBABA-2859222

## What is CVE-2022-25845?

CVE-2022-25845 is a high-severity unsafe deserialization vulnerability in com.alibaba:fastjson, published on 10 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The package com.alibaba:fastjson before 1.2.83 are vulnerable to Deserialization of Untrusted Data by bypassing the default autoType shutdown restrictions, which is possible under certain conditions. Exploiting this vulnerability allows attacking remote servers. Workaround: If upgrading is not possible, you can enable [safeMode](https://github.com/alibaba/fastjson/wiki/fastjson_safemode).

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

2 open source packages ship an affected version, including com.alibaba:fastjson. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.alibaba:fastjson` | Maven | From 1.2.25 | 1.2.83 |
| `com.alibaba:fastjson` | Maven | From 1.2.25 | 1.2.83 |

Products: Alibaba Fastjson, Oracle Communications Cloud Native Core Unified Data Repository.

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

Upgrade com.alibaba:fastjson to 1.2.83 or later.

## Is CVE-2022-25845 being exploited?

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

Public exploit code:

- CVE-2022-25845(fastjson1.2.80) exploit in Spring Env! (github_poc): https://github.com/luelueking/CVE-2022-25845-In-Spring
- exploit by python (github_poc): https://github.com/ph0ebus/CVE-2022-25845-In-Spring
- https://github.com/nerowander/CVE-2022-25845-exploit (github_poc): https://github.com/nerowander/CVE-2022-25845-exploit
- a scenario based on CVE-2022-25845 yielding a TP for metadata based SCA but a FN if the callgraph is used (github_poc): https://github.com/scabench/fastjson-tp1fn1
- https://github.com/cuijiung/fastjson-CVE-2022-25845 (github_poc): https://github.com/cuijiung/fastjson-CVE-2022-25845

## Other vulnerabilities in com.alibaba:fastjson

- [CVE-2017-18349](https://insights.sbomify.com/CVE-2017-18349/): Improper Input Validation in alilibaba:fastjson (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-25845 is a high-severity unsafe deserialization vulnerability in com.alibaba:fastjson, published on 10 Jun 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-25845 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.alibaba:fastjson (Maven): affected from 1.2.25; fixed in 1.2.83
- com.alibaba:fastjson (Maven): affected from 1.2.25; fixed in 1.2.83

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-25845/ (Markdown: https://insights.sbomify.com/CVE-2022-25845/index.md)
```

## Sources

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

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