CVE-2014-1902
3.5 · LOWOverview
CVE-2014-1902 is a low-severity vulnerability affecting y-cam ycb004_firmware. It was published on May 14, 2015 and has a CVSS 2.0 base score of 3.5 (LOW).
This vulnerability has a CVSS 2.0 base score of 3.5, rated LOW. It can be exploited remotely over the network. Some level of privileges is required for exploitation.
Technical Description
Multiple cross-site scripting (XSS) vulnerabilities in 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 inject arbitrary web script or HTML via the (1) SYSCONTACT parameter to form/identityApply, as triggered using en/identity.asp; (2) PASSWD parameter to form/accAdd, as triggered using en/account/accedit.asp; (3) NTPSERVER parameter to form/clockApply, as triggered using en/clock.asp; (4) SERVER parameter to form/smtpclientApply, as triggered using en/smtpclient.asp; (5) SERVER parameter to form/ftpApply, as triggered using en/ftp.asp; or (6) SERVER parameter to form/httpEventApply, as triggered using en/httpevent.asp.
Remediation
Check the references section for vendor advisories and patches from y-cam. Update ycb004_firmware to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
Affected Products
| Vendor | Product | Versions | Status |
|---|
Frequently Asked Questions
What is CVE-2014-1902?
CVE-2014-1902 is a low-severity vulnerability affecting y-cam ycb004_firmware. It was published on May 14, 2015 and has a CVSS 2.0 base score of 3.5 (LOW).
How severe is CVE-2014-1902?
This vulnerability has a CVSS 2.0 base score of 3.5, rated LOW. It can be exploited remotely over the network. Some level of privileges is required for exploitation.
How do I fix or remediate CVE-2014-1902?
Check the references section for vendor advisories and patches from y-cam. Update ycb004_firmware to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2014-1902?
CyberStrike's AI-powered security agents can automatically detect CVE-2014-1902 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.
Related LOW CVEs from 2014
View all →Unspecified vulnerability in HP HP-UX Whitelisting (aka WLI) before A.01.02.02 on HP-UX B.11.31 allo
Luci in Red Hat Conga stores the user's username and password in a Base64 encoded string in the __ac
Luci in Red Hat Conga does not properly enforce the user session timeout, which might allow attacker
Red Hat JBoss Operations Network (JON) before 3.0.1 uses 0777 permissions for the root directory whe
Unspecified vulnerability in the Oracle Transportation Management component in Oracle Supply Chain P
The slapper function in chkrootkit before 0.50 does not properly quote file paths, which allows loca
Secunia CSI Agent 6.0.0.15017 and earlier, 6.0.1.1007 and earlier, and 7.0.0.21 and earlier, when ru
The lock-counter implementation in utils/mount.ecryptfs_private.c in ecryptfs-utils before 90 allows
CFNetwork in Apple OS X through 10.8.5 does not remove session cookies upon a Safari reset action, w
The Ubuntu AccountsService package before 0.6.14-1git1ubuntu1.1 does not properly drop privileges wh
The smart proxy in Foreman before 1.1 uses a umask set to 0, which allows local users to modify file
pyxtrlock before 0.1 uses an incorrect variable name, which allows physically proximate attackers to