CVE-2019-11013 json
Nimble Streamer 3.0.2-2 through 3.5.4-9 has a ../ directory traversal vulnerability.
published 2019-08-22 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-2724
- cvss
- 6.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 26.4%
- EPSS 26.4% chance of exploitation in 30 days, percentile 98%
- public exploits
- 1
- Exploit-DB, plus a Nuclei check
Summary
Nimble Streamer 3.0.2-2 through 3.5.4-9 has a ../ directory traversal vulnerability. Successful exploitation could allow an attacker to traverse the file system to access files or directories that are outside of the restricted directory on the remote server.
Timeline
- Published
- First public exploit (EDB-47301)
Exploit prediction
26.38% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-47301 Nimble Streamer 3.0.2-2 < 3.5.4-9 - Directory Traversal webapps, 2019-08-23
- Nuclei template Nimble Streamer <=3.5.4-9 - Local File Inclusion nuclei detection template
- mayaseven.com https://mayaseven.com/nimble-directory-traversal-in-nimble-streamer-version-3-0-2-2-to-3-5-4-9/ referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/154196/Nimble-Streamer-3.x-Directory-Traversal.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
mayaseven.com
/nimble-directory-traversal-in-nimble-streamer-version-3-0-2-2-to-3-5-4-9/
exploit, third-party-advisory
-
packetstormsecurity.com
/files/154196/Nimble-Streamer-3.x-Directory-Traversal.html
exploit, third-party-advisory, vdb-entry
Sources
- CVE List CVE-2019-11013
- NVD CVE-2019-11013
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.