CVE-2024-22050 json
Iodine Static File Server Path Traversal Vulnerability
published 2019-10-07 7 y ago modified 2026-11-08 25 h ago also EUVD-2019-0692 , GHSA-85rf-xh54-whp3
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 60%
- public exploits
- 0
- none known
Summary
Path traversal in the static file service in Iodine less than 0.7.33 allows an unauthenticated, remote attacker to read files outside the public folder via malicious URLs.
Patch / fix
- rubygems iodine 0.7.34
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 16 mo ago
Exploit prediction
0.92% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | iodine | <0.7.34 |
0.7.34 |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/boazsegev/iodine/commit/5558233fb7defda706b4f9c87c17759705949889
patch, web
-
github.com
/advisories/GHSA-85rf-xh54-whp3
vendor-advisory, third-party-advisory, patch
-
vulncheck.com
/advisories/vc-advisory-GHSA-85rf-xh54-whp3
third-party-advisory, patch
-
github.com
/boazsegev/iodine/security/advisories/GHSA-85rf-xh54-whp3
vendor-advisory, web
-
nvd.nist.gov
/vuln/detail/CVE-2024-22050
advisory
-
github.com
/boazsegev/iodine
package
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/iodine/CVE-2024-22050.yml
web
Sources
- CVE List CVE-2024-22050
- GitHub Advisory GHSA-85rf-xh54-whp3
- NVD CVE-2024-22050
Fencer Vulns 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.