GHSA-WQ34-7F4G-953V

Vulnerability from github – Published: 2025-12-08 22:15 – Updated: 2025-12-09 19:17
VLAI
Summary
Csla affected by Remote Code Execution via WcfProxy (NetDataContractSerializer)
Details

Impact

Versions of CSLA .NET prior to version 6 allow the use of WcfProxy. WcfProxy uses the NetDataContractSerializer (NDCS) which has known vulnerabilities that can allow remote execution of code during deserialization. NDCS itself is considered obsolete, and you should avoid using WcfProxy or upgrade to CSLA 6 or higher where this issue does not exist.

Patches

CSLA .NET version 6 and higher do not use WCF or NetDataContractSerializer.

Workarounds

If you are using a version CSLA .NET older than version 6, you should stop using WcfProxy in your data portal configuration. Doing this avoids the use of WCF and the NetDataContractSerializer, avoiding the vulnerability.

Severity
7.2 (High)
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "NuGet",
        "name": "Csla"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.0.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-66631"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-502"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-12-08T22:15:56Z",
    "nvd_published_at": "2025-12-09T16:18:22Z",
    "severity": "HIGH"
  },
  "details": "### Impact\nVersions of CSLA .NET prior to version 6 allow the use of WcfProxy. WcfProxy uses the NetDataContractSerializer (NDCS) which has known vulnerabilities that can allow remote execution of code during deserialization. NDCS itself is considered obsolete, and you should avoid using WcfProxy or upgrade to CSLA 6 or higher where this issue does not exist.\n\n### Patches\nCSLA .NET version 6 and higher do not use WCF or NetDataContractSerializer.\n\n### Workarounds\nIf you are using a version CSLA .NET older than version 6, you should stop using WcfProxy in your data portal configuration. Doing this avoids the use of WCF and the NetDataContractSerializer, avoiding the vulnerability.",
  "id": "GHSA-wq34-7f4g-953v",
  "modified": "2025-12-09T19:17:25Z",
  "published": "2025-12-08T22:15:56Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/MarimerLLC/csla/security/advisories/GHSA-wq34-7f4g-953v"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-66631"
    },
    {
      "type": "WEB",
      "url": "https://github.com/MarimerLLC/csla/issues/4001"
    },
    {
      "type": "WEB",
      "url": "https://github.com/MarimerLLC/csla/pull/4018"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/MarimerLLC/csla"
    },
    {
      "type": "WEB",
      "url": "https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/ca2310"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Csla affected by Remote Code Execution via WcfProxy (NetDataContractSerializer)"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.