CVE-2014-1901: Y-Cam camera models SD range YCB003, YCK003, and YCW003; S range YCB004, YCK004, YCW004; EyeBall YCEB03; Bullet VGA YCBL03 and YCBLB3…
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.2% (FIRST EPSS); higher than 70.2% of all records.
- No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 13, 2015
- Updated
- Jun 16, 2026
- EPSS
- 1.2% · 70th percentile
- CWE
- CWE-20
Report tools
Action score
27
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| y-cam | yceb03 firmware | cpe:2.3:o:y-cam:yceb03_firmware |
| y-cam | yceb03 | cpe:2.3:h:y-cam:yceb03 |
| y-cam | ycb004 firmware | cpe:2.3:o:y-cam:ycb004_firmware |
| y-cam | ycb004 | cpe:2.3:h:y-cam:ycb004 |
| y-cam | ycb002 firmware | cpe:2.3:o:y-cam:ycb002_firmware |
| y-cam | ycb002 | cpe:2.3:h:y-cam:ycb002 |
| y-cam | ycbl03 firmware | cpe:2.3:o:y-cam:ycbl03_firmware |
| y-cam | ycbl03 | cpe:2.3:h:y-cam:ycbl03 |
| y-cam | ycblb3 firmware | cpe:2.3:o:y-cam:ycblb3_firmware |
| y-cam | ycblb3 | cpe:2.3:h:y-cam:ycblb3 |
| y-cam | yck002 firmware | cpe:2.3:o:y-cam:yck002_firmware |
| y-cam | yck002 | cpe:2.3:h:y-cam:yck002 |
and 18 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- y-cam ycb001 firmware4.30
- y-cam ycb002 firmware4.30
- y-cam ycb003 firmware4.30
- y-cam ycb004 firmware4.30
- y-cam ycbl03all versions
- y-cam ycbl03 firmware4.30
- y-cam ycblb3all versions
- y-cam ycblb3 firmware4.30
+10 more rows
- y-cam ycblhd5 firmware4.30
- y-cam yceb03 firmware4.30
- y-cam yck002 firmware4.30
- y-cam yck003 firmware4.30
- y-cam yck004 firmware4.30
- y-cam ycw001 firmware4.30
- y-cam ycw002 firmware4.30
- y-cam ycw003 firmware4.30
- y-cam ycw004all versions
- y-cam ycw004 firmware4.30
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- C · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- C
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
AV:N/AC:L/Au:S/C:N/I:N/A:C
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.