Skip to content
Fencer Intel
high 7.5

CVE-2014-10011 in the critical feed json

Stack-based buffer overflow in UltraCamLib in the UltraCam ActiveX Control (UltraCamX.ocx) for the TRENDnet SecurView camera TV-IP422WN all…

published 11y ago modified 4mo ago also EUVD-2014-1083

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
10.1%
EPSS 10.1% chance of exploitation in 30 days, percentile 95%
public exploits
1
Exploit-DB

Summary

Stack-based buffer overflow in UltraCamLib in the UltraCam ActiveX Control (UltraCamX.ocx) for the TRENDnet SecurView camera TV-IP422WN allows remote attackers to execute arbitrary code via a long string to the (1) CGI_ParamSet, (2) OpenFileDlg, (3) SnapFileName, (4) Password, (5) SetCGIAPNAME, (6) AccountCode, or (7) RemoteHost function.

Is CVE-2014-10011 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (EDB-35363)
  2. Published

Exploit prediction

10.05% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-35363 TRENDnet SecurView Wireless Network Camera TV-IP422WN - 'UltraCamX.ocx' Stack Buffer Overflow (PoC) dos, 2014-11-25
  • securityfocus.com http://www.securityfocus.com/bid/71292 referenced PoC, tagged "exploit" by a source, unverified
  • zeroscience.mk http://www.zeroscience.mk/codes/trendnet_bof.txt referenced PoC, tagged "exploit" by a source, unverified
  • zeroscience.mk http://www.zeroscience.mk/en/vulnerabilities/ZSL-2014-5211.php referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.