Yceb03 FirmwareOperating system · Y Cam

CVE-2014-1901

MEDIUM · 6.8 CVSS v2.0 Published 2015-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Multiple ASP endpoints in Y-Cam IP cameras (SD range YCB003/YCK003/YCW003, S range YCB004/YCK004/YCW004, EyeBall YCEB03, Bullet VGA YCBL03/YCBLB3, Bullet HD 720 YCBLHD5, Classic Range YCB002/YCK002/YCW003, Original Range YCB001/YCW001) running firmware 4.30 and earlier accept malformed path, item, and emailid parameters that trigger a device reboot, causing denial of service. When chained with CVE-2014-1900, this DoS can be exploited without authentication.

MitigationUpdate affected Y-Cam devices to the latest firmware version. If firmware updates are unavailable (some models may be end-of-life), implement network segmentation and restrict web interface access to trusted networks to reduce attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Yceb03 FirmwareOperating system
Affected:= 4.30
Ycb004 FirmwareOperating system
Affected:= 4.30
Ycb002 FirmwareOperating system
Affected:= 4.30
Ycbl03 FirmwareOperating system
Affected:= 4.30
Ycbl03Hardware / appliance
Affected:all versions
Ycblb3 FirmwareOperating system
Affected:= 4.30
Ycblb3Hardware / appliance
Affected:all versions
Yck002 FirmwareOperating system
Affected:= 4.30

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
Single
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:L/Au:S/C:N/I:N/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Y-Cam device model
    Check the product label on the device, or access the web interface and look for the model number in the system information or status page
    Affected if The device model is one of: YCB003, YCK003, YCW003, YCB004, YCK004, YCW004, YCEB03, YCBL03, YCBLB3, YCBLHD5, YCB002, YCK002, YCW003, YCB001, YCW001
  2. Check firmware version
    Access the Y-Cam web interface, navigate to Settings > System > Firmware/Version, or check the status page. If unavailable via web, consult the device documentation for alternative methods like UPnP or manufacturer utility.
    Affected if The firmware version is 4.30 or earlier, or for YCBL03/YCLB3 models, any version (as these are affected across all versions)
  3. Verify web management interface accessibility
    Attempt to access the device web interface over HTTP/HTTPS from the network. Check if TCP ports 80 or 443 are listening and responding.
    Affected if The web interface is accessible from untrusted networks (the vulnerability requires sending malformed ASP requests to trigger the DoS)

The environment is affected if a Y-Cam device from the listed models is running firmware version 4.30 or earlier, or is a YCBL03/YCLB3 model at any firmware version, and the web interface is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update affected Y-Cam devices to the latest firmware version. If firmware updates are unavailable (some models may be end-of-life), implement network segmentation and restrict web interface access to trusted networks to reduce attack surface.

Fix this in Yceb03 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-1901 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-1901 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data