Remote Command Execution in SOFARPC

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2024-23636: 0.80% estimated exploitation activity in the next 30 days; percentile 56.59 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact SOFARPC defaults to using the SOFA Hessian protocol to deserialize received data, while the SOFA Hessian protocol uses a blacklist mechanism to restrict deserialization of potentially dangerous classes for security protection. But there is a gadget chain that can bypass the SOFA Hessian blacklist protection mechanism, and this gadget chain only relies on JDK and does not rely on any third-party components. Patches Fixed this issue by adding a blacklist, users can upgrade to sofarpc version 5.12.0 to avoid this issue. Workarounds SOFARPC also provides a way to add additional blacklist. Users can add some class like -Drpcserializeblacklistoverride=org.apache.xpath. to avoid this issue.

Published by the source

23 Jan 2024, 20:10 UTC

Last modified by the source

24 Jan 2024, 15:26 UTC

Source last checked

26 Oct 2026, 16:25 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7q8p-9953-pxvr

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-23636

Advisory: Remote Command Execution in SOFARPC
IDs: CVE-2024-23636, GHSA-7q8p-9953-pxvr
Record: https://patchnext.com/advisories/cve-2024-23636 (revision 1, source checked 26 Oct 2026, 16:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.alipay.sofa:rpc-sofa-boot-starter 5.12.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.alipay.sofa:rpc-sofa-boot-starter: affected < 5.12.0; fixed in 5.12.0

## Suggested inspection (read-only)
- Maven com.alipay.sofa:rpc-sofa-boot-starter: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.alipay.sofa:rpc-sofa-boot-starter.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-7q8p-9953-pxvr (GitHub-reviewed advisory GHSA-7q8p-9953-pxvr lists affected ranges: Maven com.alipay.sofa:rpc-sofa-boot-starter >=0 <5.12.0)

Commands are suggestions: review each one before running it.