dbcve.org
ShenyuApplication · Apache

CVE-2021-45029

CRITICAL · 9.8 CVSS v3.1 Published 2022-01-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Groovy Code Injection & SpEL Injection which lead to Remote Code Execution. This issue affected Apache ShenYu 2.4.0 and 2.4.1.

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 · high confidence

Apache ShenYu versions 2.4.0 and 2.4.1 contain a code injection vulnerability in their Groovy and Spring Expression Language (SpEL) processing, allowing attackers to inject and execute arbitrary code remotely, achieving full Remote Code Execution without authentication.

MitigationUpgrade Apache ShenYu to version 2.4.2 or later where the vulnerability is patched. If immediate upgrade is not possible, restrict network access to the ShenYu admin interface and implement Web Application Firewall rules to detect and block injection patterns in affected parameters.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ShenyuApplication
Affected:= 2.4.0= 2.4.1

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 installed ShenYu version
    Locate the ShenYu installation and check the version file, pom.xml, or the admin UI login page version display. Common locations: check the JAR/WAR file names, or look for version in the admin interface footer.
    Affected if The installed version is exactly 2.4.0 or exactly 2.4.1
  2. Verify ShenYu admin interface is network-accessible
    Determine if the ShenYu admin interface (typically on port 9095 or configured port) is exposed to untrusted networks or the public internet. Check firewall rules, reverse proxy configurations, and network ACLs.
    Affected if The admin interface is accessible from untrusted networks without authentication barriers
  3. Check for exposed Groovy/SpEL endpoint access logs
    Review access logs for the ShenYu application, looking for requests to endpoints that process Groovy scripts or SpEL expressions, such as /api/gateway/selector or similar plugin configuration endpoints.
    Affected if There are requests to Groovy/SpEL processing endpoints from unauthenticated sources in the logs

You are affected if your installed Apache ShenYu version is 2.4.0 or 2.4.1 and the admin interface or its Groovy/SpEL processing endpoints are network-accessible to untrusted users.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Apache ShenYu to version 2.4.2 or later where the vulnerability is patched. If immediate upgrade is not possible, restrict network access to the ShenYu admin interface and implement Web Application Firewall rules to detect and block injection patterns in affected parameters.

Recommended fix Moderate confidence

Apache ShenYu 2.4.2 or later

  1. 1. Identify all deployed instances running Apache ShenYu versions 2.4.0 or 2.4.1
  2. 2. Back up all configuration files and data before upgrading
  3. 3. Plan a maintenance window as the upgrade will require service restart
  4. 4. Upgrade Apache ShenYu to version 2.4.2 or later which contains the fix for the Groovy Code Injection and SpEL Injection vulnerability
  5. 5. Verify the upgrade was successful by checking the version number in the admin UI or startup logs
  6. 6. Test critical workflows to ensure the upgrade did not break existing functionality
Caveat Review release notes for any configuration or API changes between 2.4.x versions; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Shenyu Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-45029 — 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-2021-45029 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