# CVE-2014-3895: Auth bypass in n/a

> Remote attackers can bypass authentication on I-O DATA cameras to access sensitive credentials and configuration data.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2p6f-qh49-9c92

## What is CVE-2014-3895?

CVE-2014-3895 is a medium-severity authentication bypass vulnerability in n/a, published on 29 Jul 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2014-3895?

It affects 12 products.


Products: 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.

## How do I fix CVE-2014-3895?

No fix has been published for CVE-2014-3895 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-3895 being exploited?

There is no known exploitation of CVE-2014-3895 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-3895 and fix it if it is affected.

What it is: CVE-2014-3895 is a medium-severity authentication bypass vulnerability in n/a, published on 29 Jul 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-3895 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-3895/ (Markdown: https://insights.sbomify.com/CVE-2014-3895/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-3895
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-3895
- OSV: https://osv.dev/vulnerability/CVE-2014-3895

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-3895/
Summaries are generated and may contain mistakes; the official description above is the record.