dbcve.org
SofarpcApplication · Sofastack

CVE-2023-41331

CRITICAL · 9.8 CVSS v3.1 Published 2023-09-12
Fix available
A fix is available. Upgrade to 5.11.0 or later.
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
SOFARPC is a Java RPC framework. Versions prior to 5.11.0 are vulnerable to remote command execution. Through a carefully crafted payload, an attacker can achieve JNDI injection or system command execution. In the default configuration of the SOFARPC framework, a blacklist is used to filter out dangerous classes encountered during the deserialization process. However, the blacklist is not comprehensive, and an actor can exploit certain native JDK classes and common third-party packages to construct gadget chains capable of achieving JNDI injection or system command execution attacks. Version 5.11.0 contains a fix for this issue. As a workaround, users can add `-Drpc_serialize_blacklist_override=javax.sound.sampled.AudioFileFormat` to the blacklist.

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

SOFARPC versions prior to 5.11.0 are vulnerable to deserialization attacks due to an incomplete blacklist that filters dangerous classes during the deserialization process. Attackers can exploit certain native JDK classes and common third-party package gadgets to construct chains capable of JNDI injection or arbitrary system command execution, achieving remote code execution.

MitigationUpgrade to SOFARPC version 5.11.0 or later, or apply the workaround by adding `-Drpc_serialize_blacklist_override=javax.sound.sampled.AudioFileFormat` to the serialization blacklist.

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
SofarpcApplication
Affected:< 5.11.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
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. Locate SOFARPC installation
    Search for sofarpc JAR files in the application directory, check Maven/Gradle dependency files (pom.xml, build.gradle), or examine the classpath for com.alipay.sofa.rpc classes
    Affected if SOFARPC library files or dependencies are found in the environment
  2. Identify SOFARPC version
    Inspect the sofarpc JAR file manifest (META-INF/MANIFEST.MF), check the version in pom.xml or build.gradle dependencies, or run: jar -xf sofarpc-x.x.x.jar META-INF/MANIFEST.MF && cat META-INF/MANIFEST.MF
    Affected if The discovered version is below 5.11.0 (for example 5.10.x, 5.9.x, etc.)
  3. Confirm SOFARPC serialization is in use
    Review application configuration files (rpc-config.json, sofa-rpc.xml, or YAML configs) for service references or provider definitions, or inspect network traffic for SOFARPC protocol communication
    Affected if The application exposes or consumes SOFARPC services, which requires serialization of data
  4. Check serialization blacklist configuration
    Examine JVM startup arguments or application properties for rpc_serialize_blacklist_override or similar serialization security settings, review configuration files for custom blacklist entries
    Affected if The blacklist override is not configured (the vulnerability exists in the default blacklist prior to 5.11.0)

The environment is affected if SOFARPC versions below 5.11.0 are in use and the application performs RPC serialization, which is the default behavior of SOFARPC.

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
Upgrade available Upgrade to 5.11.0 or later
Fixed in 5.11.0
Interim mitigation

Upgrade to SOFARPC version 5.11.0 or later, or apply the workaround by adding `-Drpc_serialize_blacklist_override=javax.sound.sampled.AudioFileFormat` to the serialization blacklist.

Recommended fix High confidence

5.11.0

  1. Download SOFARPC version 5.11.0 or later from the official GitHub repository
  2. Update your project's Maven or Gradle dependency to include SOFARPC version 5.11.0
  3. Rebuild your application with the updated dependency
  4. Redeploy the rebuilt application to your production environment
  5. Verify the fix by testing that previously vulnerable gadget chains (e.g., using javax.sound.sampled.AudioFileFormat) are now blocked

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

Fix this in Sofarpc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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