dbcve.org
ShenyuApplication · Apache

CVE-2022-42735

HIGH · 8.8 CVSS v3.1 Published 2023-02-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
Improper Privilege Management vulnerability in Apache Software Foundation Apache ShenYu. ShenYu Admin allows low-privilege low-level administrators create users with higher privileges than their own. This issue affects Apache ShenYu: 2.5.0. Upgrade to Apache ShenYu 2.5.1 or apply patch https://github.com/apache/shenyu/pull/3958 https://github.com/apache/shenyu/pull/3958 .

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

Improper Privilege Management vulnerability in Apache ShenYu Admin allows low-privilege administrators to create users with higher privileges than their own, enabling privilege escalation. This is a broken access control issue in the user creation functionality.

MitigationUpgrade to Apache ShenYu 2.5.1 or apply the patch from pull request #3958 to enforce proper privilege boundaries during user creation.

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.5.0

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 Apache Shenyu version
    Check the version file or startup logs for Apache Shenyu. Common locations: version in pom.xml, startup banner, or docker image tag. Run: java -jar shenyu-admin.jar --version or check the manifest/META-INF/MANIFEST.MF file inside the JAR.
    Affected if The installed version is exactly 2.5.0
  2. Confirm Shenyu Admin is deployed
    Verify that the shenyu-admin component is running. Check process list for shenyu-admin or check if port 9095 (default admin port) is listening: netstat -tlnp | grep 9095 or curl http://localhost:9095actuator/health
    Affected if The Admin module is exposed and accessible on the network
  3. Verify user creation endpoint exists
    Check if the user management API endpoint is available. Inspect the deployed shenyu-admin web application for the /user or /shadow/user endpoint handlers. Review the application's API documentation or WAR/JAR contents for user creation functionality.
    Affected if The user creation endpoint exists and accepts POST requests
  4. Review admin role permissions
    Examine the role definitions and permission matrix in the Shenyu Admin configuration. Check authentication/authorization configuration files or database tables that define what privileges a low-privilege administrator account possesses versus what privileges can be assigned during user creation.
    Affected if Low-privilege admin accounts exist and can access the user creation interface

A user is affected if they are running Apache Shenyu version 2.5.0 with the Admin module deployed and accessible, where low-privilege administrators can access the user creation functionality.

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 to Apache ShenYu 2.5.1 or apply the patch from pull request #3958 to enforce proper privilege boundaries during user creation.

Recommended fix High confidence

Apache ShenYu 2.5.1

  1. Back up your existing Apache ShenYu 2.5.0 database and configuration files
  2. Download Apache ShenYu version 2.5.1 from the official Apache release repository
  3. Review the release notes and upgrade guide for any migration requirements
  4. Stop the running ShenYu Admin service
  5. Replace the ShenYu installation with version 2.5.1
  6. Run any database migration scripts if required by the release notes
  7. Start the ShenYu Admin service
  8. Verify that the privilege escalation vulnerability is fixed by attempting to create a higher-privilege user with a low-privilege account

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

Fix this in Shenyu Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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