# CVE-2024-6645: WuKongOpenSource Wukong_nocode AviatorScript ExpressionUtil.java deserialization

> Remote attackers can exploit unsafe deserialization in AviatorScript to execute arbitrary code on the Wukong nocode platform.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-g4m4-xx42-vc78

## What is CVE-2024-6645?

CVE-2024-6645 is a medium-severity unsafe deserialization vulnerability in WuKongOpenSource Wukong_nocode, published on 10 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in WuKongOpenSource Wukong_nocode up to 20230807. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file ExpressionUtil.java of the component AviatorScript Handler. The manipulation leads to deserialization. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The associated identifier of this vulnerability is VDB-271051.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2024-6645?


## How do I fix CVE-2024-6645?

No fix has been published for CVE-2024-6645 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-6645 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6645 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6645 and fix it if it is affected.

What it is: CVE-2024-6645 is a medium-severity unsafe deserialization vulnerability in WuKongOpenSource Wukong_nocode, published on 10 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6645 exists.

Affected product: WuKongOpenSource Wukong_nocode. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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