Quick answers
- Is CVE-2024-51758 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2024-51758 being exploited in the wild.
- How severe is CVE-2024-51758?
- Low severity, with a CVSS score of 3.1, published 7 November 2024.
- Which products and versions are affected?
- filament/actions (Packagist) >= 3.2.0, < 3.2.123, ECOSYSTEM:introduced=3.2.0,fixed=3.2.123.
- Is there a fix for CVE-2024-51758?
- Yes. filament/actions (Packagist): upgrade to 3.2.123 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2024-51758 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2024-51758?
- Check whether you run filament/actions (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- filament/actions (Packagist): upgrade to 3.2.123 or later
composer require filament/actions:^3.2.123
Technical details
Filament (specifically the filament/actions package) uses an insecure default configuration for its export feature. By default, the 'default_filesystem_disk' is set to 'public', which causes exported files—often containing sensitive data—to be stored in a web-accessible directory. While many production environments use S3 or other secure drivers, installations relying on the default local 'public' disk are vulnerable to information disclosure. An attacker with network access could potentially discover and download these exported files. The fix, introduced in version 3.2.123, automatically swaps the export disk to 'local' if 'public' is detected as the default.
Affected products
- Filament filament/actions >= 3.2.0, < 3.2.123
Identifiers
- CVE-2024-51758
- GHSA-4hxw-gc2q-f6f3
Timeline
- 2024-11-07: disclosed
- 2024-11-07: advisory
- 2024-11-07: patched