CVE-2013-1604 json
Directory traversal vulnerability in MayGion IP Cameras with firmware before 2013.04.22 (05.53) allows remote attackers to read arbitrary f…
published 12y ago modified 4mo ago also EUVD-2013-1640
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.5%
- EPSS 3.5% chance of exploitation in 30 days, percentile 89%
- public exploits
- 1
- Exploit-DB
Summary
Directory traversal vulnerability in MayGion IP Cameras with firmware before 2013.04.22 (05.53) allows remote attackers to read arbitrary files via a .. (dot dot) in the default URI.
Is CVE-2013-1604 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (EDB-25813)
- Published
Exploit prediction
3.53% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-25813 MayGion IP Cameras Firmware 09.27 - Multiple Vulnerabilities webapps, 2013-05-29
- seclists.org http://seclists.org/fulldisclosure/2013/May/194 referenced PoC, tagged "exploit" by a source, unverified
- coresecurity.com http://www.coresecurity.com/advisories/maygion-IP-cameras-multiple-vulnerabilities referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/60192 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
exploit-db.com
/exploits/25813
exploit
-
seclists.org
/fulldisclosure/2013/May/194
mailing-list, exploit
-
coresecurity.com
/advisories/maygion-IP-cameras-multiple-vulnerabilities
exploit
-
securityfocus.com
/bid/60192
vdb-entry, exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/84589
vdb-entry
Sources
- CVE List CVE-2013-1604
- NVD CVE-2013-1604
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.