CVE-2024-30851 json
Directory Traversal vulnerability in codesiddhant Jasmin Ransomware v.1.0.1 allows an attacker to obtain sensitive information via the down…
published 2024-05-03 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-28769
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.6%
- EPSS 4.6% chance of exploitation in 30 days, percentile 91%
- public exploits
- 2
- Metasploit
Summary
Directory Traversal vulnerability in codesiddhant Jasmin Ransomware v.1.0.1 allows an attacker to obtain sensitive information via the download_file.php component.
Timeline
- First public exploit (Metasploit auxiliary/gather/jasmin_ransomware_dir_traversal)
- Published
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
4.61% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit auxiliary/gather/jasmin_ransomware_dir_traversal Jasmin Ransomware Web Server Unauthenticated Directory Traversal metasploit auxiliary, normal rank, 2023-04-08
- Metasploit auxiliary/gather/jasmin_ransomware_sqli Jasmin Ransomware Web Server Unauthenticated SQL Injection metasploit auxiliary, normal rank, 2023-04-08
- github.com https://github.com/chebuya/CVE-2024-30851-jasmin-ransomware-path-traversal-poc referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/chebuya/CVE-2024-30851-jasmin-ransomware-path-traversal-poc
exploit, issue-tracking, third-party-advisory
-
github.com
/codesiddhant/Jasmin-Ransomware
product
Sources
- CVE List CVE-2024-30851
- NVD CVE-2024-30851
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.