# CVE-2014-1901: Denial of service in n/a

> Remote attackers can cause a denial of service by sending malformed parameters to specific web endpoints, potentially without authentication if combined with another vulnerability.

- **Severity:** Medium 6.8 (`AV:N/AC:L/Au:S/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-p4p2-9243-q64x

## What is CVE-2014-1901?

CVE-2014-1901 is a medium-severity denial of service vulnerability in n/a, published on 14 May 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Y-Cam camera models SD range YCB003, YCK003, and YCW003; S range YCB004, YCK004, YCW004; EyeBall YCEB03; Bullet VGA YCBL03 and YCBLB3; Bullet HD 720 YCBLHD5; Y-cam Classic Range YCB002, YCK002, and YCW003; and Y-cam Original Range YCB001, YCW001, running firmware 4.30 and earlier, allow remote authenticated users to cause a denial of service (reboot) via a malformed (1) path parameter to en/store_main.asp, (2) item parameter to en/account/accedit.asp, or (3) emailid parameter to en/smtpclient.asp.  NOTE: this issue can be exploited without authentication by leveraging CVE-2014-1900.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 18 products.


Products: Y-Cam Ycb001 Firmware, Y-Cam Ycb002 Firmware, Y-Cam Ycb003 Firmware, Y-Cam Ycb004 Firmware, Y-Cam Ycbl03, Y-Cam Ycbl03 Firmware, Y-Cam Ycblb3, Y-Cam Ycblb3 Firmware, Y-Cam Ycblhd5 Firmware, Y-Cam Yceb03 Firmware, Y-Cam Yck002 Firmware, Y-Cam Yck003 Firmware, Y-Cam Yck004 Firmware, Y-Cam Ycw001 Firmware, Y-Cam Ycw002 Firmware, Y-Cam Ycw003 Firmware, Y-Cam Ycw004, Y-Cam Ycw004 Firmware.

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

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

## Is CVE-2014-1901 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-1900](https://insights.sbomify.com/CVE-2014-1900/): Auth bypass in n/a (medium 5.0)
- [CVE-2014-1902](https://insights.sbomify.com/CVE-2014-1902/): Cross-site scripting in n/a (low 3.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-1901 is a medium-severity denial of service vulnerability in n/a, published on 14 May 2015. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-1901 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-1901/ (Markdown: https://insights.sbomify.com/CVE-2014-1901/index.md)
```

## Sources

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

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