dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-6645

MEDIUM · 6.3 CVSS v3.1 Published 2024-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A deserialization vulnerability exists in the AviatorScript Handler's ExpressionUtil.java component of the WuKong Wukong_nocode platform. Attackers can exploit unsafe deserialization through crafted malicious expressions processed by AviatorScript, potentially leading to remote code execution.

MitigationImplement input validation and sanitization on all expressions before processing by AviatorScript, or upgrade to a patched version if available. Consider using a safe expression evaluator if the vulnerability cannot be remediated through library updates.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if WuKong Wukong_nocode platform is installed
    Search for the application installation directory, check for files named 'wukong', 'Wukong', or the platform's characteristic directory structure. Look for JAR files or WAR files containing 'wukong' in the filename.
    Affected if The WuKong Wukong_nocode platform is present in the environment
  2. Locate the AviatorScript library version
    Search for AviatorScript JAR files (typically named 'aviator-*version*.jar') within the application's lib directory, WEB-INF/lib folder, or classpath. Check the manifest files or POM dependencies if available.
    Affected if AviatorScript library is present in the application's classpath
  3. Identify ExpressionUtil.java component usage
    Search for ExpressionUtil.java class file or source code within the application codebase. Check if the AviatorScript Handler module is loaded by inspecting the application's class loading configuration or module dependencies.
    Affected if The AviatorScript Handler and ExpressionUtil component are being used by the application
  4. Verify expression processing is enabled
    Inspect application configuration files (e.g., XML, YAML, or properties files) for expressions that invoke AviatorScript, such as 'aviator', 'expression', or custom expression evaluation handlers. Check runtime logs for AviatorScript expression execution.
    Affected if Expressions are being processed through AviatorScript in the application
  5. Compare installed versions against known vulnerable versions
    Consult the vendor's security advisory or NVD entry for CVE-2024-6645 to obtain the specific version ranges marked as vulnerable. Compare the identified AviatorScript version and WuKong platform version against those ranges.
    Affected if The installed versions fall within the known vulnerable version ranges for this CVE

The environment is affected if the WuKong Wukong_nocode platform is running with AviatorScript Handler enabled and the installed versions match the vulnerable ranges specified for CVE-2024-6645.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement input validation and sanitization on all expressions before processing by AviatorScript, or upgrade to a patched version if available. Consider using a safe expression evaluator if the vulnerability cannot be remediated through library updates.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6645 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-6645 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data