Menu

Star on GitHub · 3.2k

CVE-2016-2380

3.1 · LOW

An information leak exists in the handling of the MXIT protocol in Pidgin.

Published Jan 6, 2017CWE-125EPSS 1.75%

Overview

CVE-2016-2380 is a low-severity vulnerability. It was published on January 6, 2017 and has a CVSS 3.0 base score of 3.1 (LOW).

This vulnerability has a CVSS 3.0 base score of 3.1, rated LOW. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

An information leak exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT data sent to the server could potentially result in an out-of-bounds read. A user could be convinced to enter a particular string which would then get converted incorrectly and could lead to a potential out-of-bounds read.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2016-2380?

CVE-2016-2380 is a low-severity vulnerability. It was published on January 6, 2017 and has a CVSS 3.0 base score of 3.1 (LOW).

How severe is CVE-2016-2380?

This vulnerability has a CVSS 3.0 base score of 3.1, rated LOW. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2016-2380?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2016-2380?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2016-2380 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related LOW CVEs from 2016

View all