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.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2016
- CVE-2016-2365A denial of service vulnerability exists in the handling of …
- CVE-2016-2366A denial of service vulnerability exists in the handling of …
- CVE-2016-2367An information leak exists in the handling of the MXIT proto…
- CVE-2016-2368Multiple memory corruption vulnerabilities exist in the hand…
- CVE-2016-2369A NULL pointer dereference vulnerability exists in the handl…
- CVE-2016-2370A denial of service vulnerability exists in the handling of …
- CVE-2016-2372An information leak exists in the handling of the MXIT proto…
- CVE-2016-2373A denial of service vulnerability exists in the handling of …
- CVE-2016-2374An exploitable memory corruption vulnerability exists in the…
- CVE-2016-2375An exploitable out-of-bounds read exists in the handling of …
- CVE-2016-2376A buffer overflow vulnerability exists in the handling of th…
- CVE-2016-2377A buffer overflow vulnerability exists in the handling of th…
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