dbcve.org
ShenyuApplication · Apache

CVE-2023-25753

MEDIUM · 6.5 CVSS v3.1 Published 2023-10-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
There exists an SSRF (Server-Side Request Forgery) vulnerability located at the /sandbox/proxyGateway endpoint. This vulnerability allows us to manipulate arbitrary requests and retrieve corresponding responses by inputting any URL into the requestUrl parameter. Of particular concern is our ability to exert control over the HTTP method, cookies, IP address, and headers. This effectively grants us the capability to dispatch complete HTTP requests to hosts of our choosing. This issue affects Apache ShenYu: 2.5.1. Upgrade to Apache ShenYu 2.6.0 or apply patch  https://github.com/apache/shenyu/pull/4776  .

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 contains an SSRF vulnerability in the /sandbox/proxyGateway endpoint where the requestUrl parameter accepts arbitrary URLs, allowing attackers to control the HTTP method, cookies, IP address, and headers. This enables dispatching complete HTTP requests to internal services, cloud metadata endpoints, or external systems.

MitigationUpgrade Apache ShenYu to version 2.6.0 or apply the patch from pull request #4776 which adds proper validation/sanitization to the requestUrl parameter to prevent arbitrary URL injection.

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.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
Low
Integrity
Low
Availability
None

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

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 Apache ShenYu version
    Check the ShenYu version file or startup logs. Common locations: look for version in pom.xml, build.gradle, or check the admin UI if accessible. Run: grep -r 'shenyu.version' or check the JAR/WAR file manifest.
    Affected if The installed version is 2.5.1 exactly (this is the only affected version listed)
  2. Locate the ShenYu deployment
    Identify if the ShenYu admin or gateway service is deployed. Check for shenyu-admin or shenyu-gateway JAR/WAR files, Docker containers, or service processes running on ports 9095 (admin) or 8088 (gateway).
    Affected if Apache ShenYu is deployed in the environment regardless of version (to then check the endpoint)
  3. Verify /sandbox/proxyGateway endpoint accessibility
    Attempt to access the /sandbox/proxyGateway endpoint on the gateway (typically port 8088) or admin (port 9095). Send a GET request: curl -s -o /dev/null -w '%{http_code}' http://<host>:8088/sandbox/proxyGateway
    Affected if The endpoint responds (any HTTP status, including 400/404 indicates the endpoint exists)
  4. Test requestUrl parameter for SSRF
    Send a request to /sandbox/proxyGateway with a test URL parameter: curl -X POST 'http://<host>:8088/sandbox/proxyGateway' -d 'requestUrl=http://127.0.0.1:9999/test'. Check if the server attempts to connect to the provided URL.
    Affected if The server attempts to fetch or connect to the URL provided in requestUrl parameter without validation (response includes data from the target URL or connection error from an internal address)
  5. Check network exposure of the endpoint
    Review firewall rules, API gateway configurations, or load balancer settings to determine if /sandbox/proxyGateway is accessible from untrusted networks or the internet. Check if the endpoint requires authentication.
    Affected if The /sandbox/proxyGateway endpoint is exposed to untrusted networks (internet or non-admin users) without proper authentication

You are affected if running Apache ShenYu version 2.5.1 and the /sandbox/proxyGateway endpoint is accessible without proper validation of the requestUrl parameter.

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.6.0 or apply the patch from pull request #4776 which adds proper validation/sanitization to the requestUrl parameter to prevent arbitrary URL injection.

Recommended fix High confidence

Apache ShenYu 2.6.0

  1. Download Apache ShenYu version 2.6.0 from the official Apache releases repository (https://downloads.apache.org/shenyu/)
  2. Follow the standard upgrade documentation for migrating from version 2.5.1 to 2.6.0
  3. Ensure the /sandbox/proxyGateway endpoint is properly tested after upgrade to confirm the SSRF vulnerability is patched
  4. Verify that the requestUrl parameter no longer allows arbitrary URL manipulation
Caveat Review release notes for 2.6.0 to check for any breaking changes or configuration adjustments needed for your specific deployment

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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