CVE-2014-3895 iodata: Improper Authentication
iodata: no CVSS score yet. EPSS 2.2% estimated probability of exploitation activity in the next 30 days.
On this page
The I-O DATA TS-WLCAM camera with firmware 1.06 and earlier, TS-WLCAM/V camera with firmware 1.06 and earlier, TS-WPTCAM camera with firmware 1.08 and earlier, TS-PTCAM camera with firmware 1.08 and earlier, TS-PTCAM/POE camera with firmware 1.08 and earlier, and TS-WLC2 camera with firmware 1.02 and earlier allow remote attackers to bypass authentication, and consequently obtain sensitive credential and configuration data, via unspecified vectors.
- EPSS
- 2.2% (unchanged from 2.2% a week ago; 2.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 83rd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-287 Improper Authentication
- OWASP Top 10
- A07:2025 Authentication Failures
- Published
- Modified
- NVD analysis
- Analyzed, since modified
- Record from
- the NVD, synced
Fix and patched versions
- Vendor advisory: http://www.iodata.jp/support/information/2014/qwatch/
Ask an AI about this CVE
Show the prompt
Explain CVE-2014-3895 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2014-3895?via=ask-ai-copy and https://cve.bz/cve/CVE-2014-3895?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2014-3895 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
- iodata:ts-ptcam\/poe_camera
- iodata:ts-ptcam\/poe_camera_firmware
- iodata:ts-ptcam_camera
- iodata:ts-ptcam_camera_firmware
- iodata:ts-wlc2_camera
- iodata:ts-wlc2_camera_firmware
- iodata:ts-wlcam\/v_camera
- iodata:ts-wlcam\/v_camera_firmware
- iodata:ts-wlcam_camera
- iodata:ts-wlcam_camera_firmware
- iodata:ts-wptcam_camera
- iodata:ts-wptcam_camera_firmware
Versions
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| iodata:ts-wlcam/v_camera_firmware | through 1.0.6 |
| iodata:ts-wptcam_camera_firmware | through 1.0.8 |
| iodata:ts-wlcam_camera_firmware | through 1.06 |
| iodata:ts-ptcam/poe_camera_firmware | through 1.08 |
| iodata:ts-wlc2_camera_firmware | through 1.02 |
| iodata:ts-ptcam_camera_firmware | through 1.08 |
Attack patterns (CAPEC)
- CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
- CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
- CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
- CAPEC-114 Authentication Abuse Severity: Medium
- CAPEC-115 Authentication Bypass Severity: Medium
- CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
- CAPEC-194 Fake the Source of Data Severity: Medium
- CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High
- CAPEC-633 Token Impersonation Severity: Medium
- CAPEC-650 Upload a Web Shell to a Web Server Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.