CVE-2013-2574 in the critical feed json
An Access vulnerability exists in FOSCAM IP Camera FI8620 due to insufficient access restrictions in the /tmpfs/ and /log/ directories, whi…
published 6y ago modified 4mo ago also EUVD-2013-2516
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 29.6%
- EPSS 29.6% chance of exploitation in 30 days, percentile 98%
- public exploits
- 1
- Exploit-DB
Summary
An Access vulnerability exists in FOSCAM IP Camera FI8620 due to insufficient access restrictions in the /tmpfs/ and /log/ directories, which could let a malicious user obtain sensitive information.
Is CVE-2013-2574 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-27076)
- Published
Exploit prediction
29.59% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-27076 FOSCAM IP-Cameras - Improper Access Restrictions webapps, 2013-07-24
- coresecurity.com http://www.coresecurity.com/advisories/foscam-ip-cameras-improper-access-restrictions referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
-
exploit-db.com
/exploits/27076
exploit, third-party-advisory, vdb-entry
-
coresecurity.com
/advisories/foscam-ip-cameras-improper-access-restrictions
exploit, third-party-advisory
-
securityfocus.com
/bid/61415
third-party-advisory, vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/85941
third-party-advisory, vdb-entry
-
packetstormsecurity.com
/files/cve/CVE-2013-2574
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2013-2574
- NVD CVE-2013-2574
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.