CVE-2024-47049 json
czim/file-handling vulnerable to SSRF and directory traversal
published 2y ago modified 4mo ago also GHSA-6rgh-r6j3-3223 , EUVD-2024-2738
- cvss
- 8.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
The czim/file-handling package before 1.5.0 and 2.x before 2.3.0 (used with PHP Composer) does not properly validate URLs within makeFromUrl and makeFromAny, leading to SSRF, and to directory traversal for the reading of local files.
Patch / fix
- packagist czim/file-handling 1.5.0, 2.3.0
- czim file-handling 1.5.0, 2.3.0
Is CVE-2024-47049 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.64% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N |
| NVD | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N |
| CNA | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N |
| GitHub | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | czim/file-handling | <1.5.0 >=2.0.0, <2.3.0 |
1.5.0 2.3.0 |
Classification
References
-
github.com
/czim/file-handling/commit/95dfda850536bf35e684619598b9d02f4c97680d
web
-
github.com
/czim/file-handling/commit/dcf879896efe3457f51af9c8eab9f70dfc709a99
web
-
github.com
/czim/file-handling/blob/2.3.0/SECURITY.md
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2024-47049
advisory
-
github.com
/czim/file-handling
package
Sources
- CVE List CVE-2024-47049
- GitHub Advisory GHSA-6rgh-r6j3-3223
- NVD CVE-2024-47049
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.