CVE-2017-12969 in the critical feed json
Buffer overflow in the ViewerCtrlLib.ViewerCtrl ActiveX control in Avaya IP Office Contact Center before 10.1.1 allows remote attackers to…
published 2017-11-09 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-4490
- cvss
- 8.8
- version 3.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
Buffer overflow in the ViewerCtrlLib.ViewerCtrl ActiveX control in Avaya IP Office Contact Center before 10.1.1 allows remote attackers to cause a denial of service (heap corruption and crash) or execute arbitrary code via a long string to the open method.
Timeline
- First public exploit (EDB-43120)
- Published
Exploit prediction
10.08% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-43120 Avaya IP Office (IPO) < 10.1 - ActiveX Buffer Overflow dos, 2017-11-05
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
exploit-db.com
/exploits/43120/
exploit, third-party-advisory, vdb-entry
-
downloads.avaya.com
/css/P8/documents/101044091
vendor-advisory
- hyp3rlinx.altervista.org /advisories/AVAYA-OFFICE-IP-%28IPO%29-v9.1.0-10.1-VIEWERCTRL-ACTIVE-X-BUFFER-OVERFLOW-0DAY.txt
-
packetstormsecurity.com
/files/144882/Avaya-IP-Office-IPO-10.1-Active-X-Buffer-Overflow.html
third-party-advisory, vdb-entry
-
securityfocus.com
/bid/101667
vdb-entry, third-party-advisory
-
seclists.org
/fulldisclosure/2017/Nov/17
mailing-list, third-party-advisory
Sources
- CVE List CVE-2017-12969
- NVD CVE-2017-12969
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.