Skip to content

← Public intelligence

Maven package

com.alipay.sofa:hessian

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.1MavenPublished

    SOFA Hessian Remote Command Execution (RCE) Vulnerability

    CVE-2024-46983 · GHSA-c459-2m73-67hj

    Affected
    • Maven com.alipay.sofa:hessian < 3.5.5
    Fixed in
    3.5.5· Vendor fix available
    Issue
    Impact 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 update blacklist, users can upgrade to sofahessian version 3.5.5 to avoid this issue. Workarounds You can maintain a blacklist yourself in this directory external/serialize.blacklist.

    Recommended action: Upgrade to 3.5.5 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Critical, CVSS 9.8MavenPublished

    Incomplete List of Disallowed Inputs in SOFA-Hessian

    CVE-2019-9212 · GHSA-pfwp-8pq4-g7pv

    Affected
    • Maven com.alipay.sofa:hessian >= 4.0.0, < 4.0.2; < 3.3.6
    Fixed in
    4.0.23.3.6· Vendor fix available
    Issue
    SOFA-Hessian through 4.0.2 allows remote attackers to execute arbitrary commands via a crafted serialized Hessian object because blacklisting of com.caucho.naming.QName and com.sun.org.apache.xpath.internal.objects.XString is mishandled, related to Resin Gadget.

    Recommended action: Upgrade to 4.0.2 or 3.3.6 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →