CVE-2017-8225 in the critical feed json
On Wireless IP Camera (P2P) WIFICAM devices, access to .ini files (containing credentials) is not correctly checked.
published 2017-04-25 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-17187
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 35.4%
- EPSS 35.4% chance of exploitation in 30 days, percentile 98%
- public exploits
- 1
- Exploit-DB, plus a Nuclei check
Summary
On Wireless IP Camera (P2P) WIFICAM devices, access to .ini files (containing credentials) is not correctly checked. An attacker can bypass authentication by providing an empty loginuse parameter and an empty loginpas parameter in the URI.
Timeline
- First public exploit (EDB-43142)
- Published
Exploit prediction
35.36% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-43142 Wireless IP Camera (P2P) WIFICAM - Remote Code Execution remote, 2017-03-08
- Nuclei template GoAhead Camera - Credential Disclosure nuclei detection template
- pierrekim.github.io https://pierrekim.github.io/blog/2017-03-08-camera-goahead-0day.html#pre-auth-info-leak-goahead referenced PoC, tagged "exploit" by a source, unverified
- seclists.org http://seclists.org/fulldisclosure/2017/Mar/23 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-522 Insufficiently Protected Credentials
References
-
pierrekim.github.io
/blog/2017-03-08-camera-goahead-0day.html#pre-auth-info-leak-goahead
exploit, third-party-advisory
-
seclists.org
/fulldisclosure/2017/Mar/23
exploit, mailing-list, third-party-advisory
Sources
- CVE List CVE-2017-8225
- NVD CVE-2017-8225
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.