Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven.NET NuGet🐍 PyPI💎 RubyGems

GHSA-j945-c44v-97g6

MEDIUM

MPXJ has a Potential Path Traversal Vulnerability

Also known asCVE-2024-49771
Published
Oct 28, 2024
Updated
Oct 30, 2024
Affected
7 pkgs
Patched
7 / 7
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk37th percentile+0.22%
0.00%0.32%0.64%0.96%0.2%0.5%Dec 25Apr 26Jun 26

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

7 pkgs affected
net.sf.mpxj:mpxj.NETnet.sf.mpxj.NETnet.sf.mpxj-for-csharp.NETnet.sf.mpxj-for-vb.NETMPXJ.Net🐍mpxj💎mpxj

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

Description

Impact

The patch for the historical vulnerability CVE-2020-35460 in MPXJ is incomplete as there is still a possibility that a malicious path could be constructed which would not be picked up by the original fix and allow files to be written to arbitrary locations.

Patches

The issue is addressed in MPXJ version 13.5.1

Workarounds

Do not pass zip files to MPXJ.

References

N/A

Credits

Issue report and patch provided by yyjLF and sprinkle

Affected Packages

7 total 7 fixed
EcosystemPackageVulnerable rangeFix
Mavennet.sf.mpxj:mpxj8.3.5&&< 13.5.113.5.1
.NETNuGetnet.sf.mpxj8.3.5&&< 13.5.113.5.1
.NETNuGetnet.sf.mpxj-for-csharp8.3.5&&< 13.5.113.5.1
.NETNuGetnet.sf.mpxj-for-vb8.3.5&&< 13.5.113.5.1
.NETNuGetMPXJ.Net13.0.0&&< 13.5.113.5.1
🐍PyPImpxj8.3.5&&< 13.5.113.5.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.sf.mpxj:mpxj. 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.

  2. Fix

    Update net.sf.mpxj:mpxj to 13.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j945-c44v-97g6 is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-j945-c44v-97g6 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-j945-c44v-97g6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact The patch for the historical vulnerability CVE-2020-35460 in MPXJ is incomplete as there is still a possibility that a malicious path could be constructed which would not be picked up by the original fix and allow files to be written to arbitrary locations. ### Patches The issue is addressed in MPXJ version 13.5.1 ### Workarounds Do not pass zip files to MPXJ. ### References N/A ### Credits Issue report and patch provided by yyjLF and sprinkle
O3 Security · Impact-Aware SCA

Is GHSA-j945-c44v-97g6 in your dependencies?

O3 detects GHSA-j945-c44v-97g6 across Maven, NuGet, PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.