CVE-2016-2371
UnknownEPSS 3.15%
Last modified
CVE-2016-2371 is a vulnerability of currently unknown severity. An out-of-bounds write vulnerability exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT data sent via the server could cause memory corruption resulting in code execution.. EPSS estimates a 3.15% chance of exploitation in the next 30 days.
Description
An out-of-bounds write vulnerability exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT data sent via the server could cause memory corruption resulting in code execution.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Pidgin | Pidgin | <= 2.10.12 |
| Canonical | Ubuntu Linux | 12.04 |
| Canonical | Ubuntu Linux | 14.04 |
| Canonical | Ubuntu Linux | 15.10 |
| Debian | Debian Linux | 8.0 |
References
- http://www.debian.org/security/2016/dsa-3620Third Party Advisory
- http://www.pidgin.im/news/security/?id=104Patch, Vendor Advisory
- http://www.securityfocus.com/bid/91335Third Party Advisory, VDB Entry
- http://www.talosintelligence.com/reports/TALOS-2016-0139/Technical Description, Third Party Advisory
- http://www.ubuntu.com/usn/USN-3031-1Third Party Advisory
- http://www.debian.org/security/2016/dsa-3620Third Party Advisory
- http://www.pidgin.im/news/security/?id=104Patch, Vendor Advisory
- http://www.securityfocus.com/bid/91335Third Party Advisory, VDB Entry
- http://www.talosintelligence.com/reports/TALOS-2016-0139/Technical Description, Third Party Advisory
- http://www.ubuntu.com/usn/USN-3031-1Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2016-2371?
An out-of-bounds write vulnerability exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT data sent via the server could cause memory corruption resulting in code execution.
How severe is CVE-2016-2371?
Severity scoring for CVE-2016-2371 is pending analysis. The EPSS model estimates a 3.15% probability of exploitation in the next 30 days.
How do I fix CVE-2016-2371?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2016-2371?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
