CVE-2016-2375

An exploitable out-of-bounds read exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT contact information sent from the server can result in memory disclosure.

Published: 2017-01-06 Last update: 2026-05-06 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2016-2375 is rated Moderate Risk (52.8/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 2.69%). EPSS rose +2.22% over the last day, indicating growing attacker interest. Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2016-2375

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.47% 2.69% +2.22%
2 2025-03-30 1.58% 0.47% -1.10%
3 2025-03-29 — 1.58% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2016-2375

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.3 3.0 MEDIUM
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 1.4 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2016-2375

OS Trackers for CVE-2016-2375

vendor priority summary link
debian not yet assigned CVE-2016-2375 not yet assigned priority: Debian including 1 source packages (pidgin), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2016-2375
gentoo normal CVE-2016-2375: 1 GLSA(s) (201701-38), 1 atom(s) (net-im/pidgin); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2016-2375
redhat medium — https://access.redhat.com/security/cve/CVE-2016-2375
suse medium — https://www.suse.com/security/cve/CVE-2016-2375/
ubuntu medium CVE-2016-2375 medium priority: Ubuntu including 1 source packages (pidgin), 5 status rows across 5 suites (precise, trusty, upstream, wily, xenial): released 5. https://ubuntu.com/security/CVE-2016-2375

Affected software / configurations for CVE-2016-2375

Vendor Product Version Raw CPE
pidgin pidgin <= 2.10.12 cpe:2.3:a:pidgin:pidgin:*:*:*:*:*:*:*:*
canonical ubuntu_linux 12.04 cpe:2.3:o:canonical:ubuntu_linux:12.04:*:*:*:lts:*:*:*
canonical ubuntu_linux 14.04 cpe:2.3:o:canonical:ubuntu_linux:14.04:*:*:*:lts:*:*:*
canonical ubuntu_linux 15.10 cpe:2.3:o:canonical:ubuntu_linux:15.10:*:*:*:*:*:*:*
debian debian_linux 8.0 cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*

References for CVE-2016-2375

cvelogic Threat Intelligence