How severe is GHSA-9xhh-3m78-gvgj?

GHSA-9xhh-3m78-gvgj has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-9xhh-3m78-gvgj?

GHSA-9xhh-3m78-gvgj affects the following packages: Csla (NuGet), Csla (NuGet), Csla (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-9xhh-3m78-gvgj?

Update Csla to 5.5.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9xhh-3m78-gvgj is resolved across your whole dependency graph.

How do I detect GHSA-9xhh-3m78-gvgj in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Csla. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-9xhh-3m78-gvgj if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-9xhh-3m78-gvgj?

O3 pinpoints whether GHSA-9xhh-3m78-gvgj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-9xhh-3m78-gvgj actively exploited in the wild?

No public exploit code has been indexed for GHSA-9xhh-3m78-gvgj yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-9xhh-3m78-gvgj?

GHSA-9xhh-3m78-gvgj has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 71th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-9xhh-3m78-gvgj published, and has it been updated?

GHSA-9xhh-3m78-gvgj was published on July 22, 2024 and was last updated on August 15, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET NuGet

GHSA-9xhh-3m78-gvgj

CRITICAL

CLSA Directory Traversal vulnerability

Also known asCVE-2024-28698

Published

Jul 22, 2024

Updated

Aug 15, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk71th percentile-7.42%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

3 pkgs affected

.NETCsla.NETCsla.NETCsla

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

Directory Traversal vulnerability in Marimer LLC CSLA .Net before 8.0 allows a remote attacker to execute arbitrary code via a crafted script to the MobileFormatter component.

Fixes for this issue have been backported to the 5.x, 6.x, and 7.x branches of CSLA. CSLA version 5.5.4 contains a fix. As of time of publication, 6.x and 7.x do not have numbered versions containing the fix but do have fix commits available.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`Csla`	all versions	5.5.4
.NETNuGet	`Csla`	≥ 6.0.0&&< 8.0.0	8.0.0
.NETNuGet	`Csla`	≥ 7.0.0&&< 8.0.0	8.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Csla. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update Csla to 5.5.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9xhh-3m78-gvgj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-9xhh-3m78-gvgj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-9xhh-3m78-gvgj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Directory Traversal vulnerability in Marimer LLC CSLA .Net before 8.0 allows a remote attacker to execute arbitrary code via a crafted script to the MobileFormatter component. Fixes for this issue have been backported to the 5.x, 6.x, and 7.x branches of CSLA. CSLA version 5.5.4 contains a fix. As of time of publication, 6.x and 7.x do not have numbered versions containing the fix but do have fix commits available.

O3 Security · Impact-Aware SCA

Is GHSA-9xhh-3m78-gvgj in your dependencies?

O3 detects GHSA-9xhh-3m78-gvgj across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works