Out-of-bounds Write Affecting pidgin-devel package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CENTOS7-PIDGINDEVEL-1958617
- published26 Jul 2021
- disclosed21 Jun 2016
Introduced: 21 Jun 2016
CVE-2016-2374 (opens in a new tab)How to fix?
There is no fixed version for Centos:7 pidgin-devel.
NVD Description
Note: Versions mentioned in the description apply only to the upstream pidgin-devel package and not the pidgin-devel package as distributed by Centos.
See How to fix? for Centos:7 relevant fixed versions and status.
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.
References
- http://www.securityfocus.com/bid/91335
- http://www.pidgin.im/news/security/?id=107
- https://access.redhat.com/security/cve/CVE-2016-2374
- http://www.debian.org/security/2016/dsa-3620
- https://security.gentoo.org/glsa/201701-38
- http://www.talosintelligence.com/reports/TALOS-2016-0142/
- http://www.ubuntu.com/usn/USN-3031-1