Menu

Star on GitHub · 3.2k

CVE-2016-2372

5.9 · MEDIUM

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

Published Jan 6, 2017CWE-125EPSS 1.76%

Overview

CVE-2016-2372 is a medium-severity vulnerability. It was published on January 6, 2017 and has a CVSS 3.0 base score of 5.9 (MEDIUM).

This vulnerability has a CVSS 3.0 base score of 5.9, rated MEDIUM. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

Technical description

An information leak exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT data sent via the server could potentially result in an out-of-bounds read. A malicious user, server, or man-in-the-middle attacker can send an invalid size for a file transfer which will trigger an out-of-bounds read vulnerability. This could result in a denial of service or copy data from memory to the file, resulting in an information leak if the file is sent to another user.

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-2372?

CVE-2016-2372 is a medium-severity vulnerability. It was published on January 6, 2017 and has a CVSS 3.0 base score of 5.9 (MEDIUM).

How severe is CVE-2016-2372?

This vulnerability has a CVSS 3.0 base score of 5.9, rated MEDIUM. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

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

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-2372?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2016-2372 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 MEDIUM CVEs from 2016

View all