CVE-2016-2374
CVE-2016-2374 Vulnerability Analysis & Exploit Intelligence
An exploitable memory corruption vulnerability exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT MultiMX message sent via the server can result in an out-of-bounds write leading to memory disclosure and code execution.
Published Updated Sources: cvelistV5, certcc
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
3%
chance of exploitation in 30 days
CVSS base
Unscored
no source published a base score
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
References
6 on the record
- www.securityfocus.com/bid/91335
vdb-entry, x_refsource_BID
- www.talosintelligence.com/reports/TALOS-2016-0142/
x_refsource_MISC
- www.debian.org/security/2016/dsa-3620
vendor-advisory, x_refsource_DEBIAN
- www.pidgin.im/news/security/?id=107
x_refsource_CONFIRM
- security.gentoo.org/glsa/201701-38
vendor-advisory, x_refsource_GENTOO
- www.ubuntu.com/usn/USN-3031-1
vendor-advisory, x_refsource_UBUNTU
Elsewhere on this site
- pidginevery CVE for this vendor
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.