CVE-2016-4323

CVE-2016-4323 describes a directory traversal in Pidgin’s MXIT protocol handling that could allow overwriting files via a crafted splash image filename sent by a server. Affected product: Pidgin (MXIT handling). Root cause: improper handling of MXIT data enabling uncontrolled file overwrite. Impa...

CVE-2016-2365

CVE-2016-2365 describes a denial-of-service in Pidgin via the MXIT protocol. The vulnerability stems from how specially crafted MXIT data is processed, potentially causing a null pointer dereference and a crash when received from a malicious server or via network interception. Affected software: ...

CVE-2016-2367

CVE-2016-2367 affects Pidgin (MXIT handling). It describes an information leak/out-of-bounds read triggered by an invalid avatar size, which could cause DoS or memory data exposure if the avatar is shared. The connected documents reiterate this CVE in various Nessus/EulerOS notes but do not provi...

CVE-2016-2368

CVE-2016-2368 involves multiple memory corruption vulnerabilities in Pidgin’s MXIT protocol handling. Specially crafted MXIT data could cause buffer overflows, potentially enabling code execution or memory disclosure. Connected sources consistently tie this to Pidgin (MXIT) and note exploitation ...

CVE-2016-2369

CVE-2016-2369 is a NULL pointer dereference in Pidgin’s MXIT protocol handling. A server can send an MXIT packet starting with a NULL byte to trigger a denial of service. Documented impact per NVD: CVSS2 base 4.3 (Partial availability impact) and CVSS3 base 5.9 (Availability impact, network/vecto...

CVE-2016-2372

CVE-2016-2372 concerns an information leak/out-of-bounds read in Pidgin due to MXIT protocol handling. Specifically, a malicious party can send an invalid file-transfer size, potentially triggering an out-of-bounds read that may cause a denial of service or allow copying memory contents to a file...

CVE-2016-2373

CVE-2016-2373 affects the Pidgin MXIT protocol handling. Across connected sources, a malicious server or user can send specially crafted MXIT data (e.g., invalid mood) that can trigger a crash through a null pointer dereference or an out-of-bounds read/write in the MXIT processing, depending on t...

CVE-2016-2375

CVE-2016-2375 affects Pidgin via an out-of-bounds read in MXIT handling that can disclose memory contents. The connected references confirm this CVE is tied to Pidgin’s MXIT processing and memory disclosure. No specific patch version or remediation details are provided in the supplied documents; ...

CVE-2016-2377

CVE-2016-2377 concerns a buffer overflow in the MXIT protocol handling in Pidgin. Specifically, specially crafted MXIT data or a server response with a negative content-length can trigger an out-of-bounds write of one byte, potentially enabling memory corruption. The available connected documents...

CVE-2016-2373

A denial of service vulnerability 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 server or user can send an invalid mood to trigger this vulnerability...

CVE-2016-2377

A buffer overflow vulnerability exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT data sent by the server could potentially result in an out-of-bounds write of one byte. A malicious server can send a negative content-length in response to a HTTP request triggering the...

CVE-2016-4323

A directory traversal exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT data sent from the server could potentially result in an overwrite of files. A malicious server or someone with access to the network traffic can provide an invalid filename for a splash image...

CVE-2016-2368

Multiple memory corruption vulnerabilities exist in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT data sent via the server could result in multiple buffer overflows, potentially resulting in code execution or memory disclosure...

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...

CVE-2016-2372

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...

CVE-2016-2365

A denial of service vulnerability exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT data sent via the server could potentially result in a null pointer dereference. A malicious server or an attacker who intercepts the network traffic can send invalid data to trigger th...

CVE-2016-2370

A denial of service vulnerability exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT data sent from the server could potentially result in an out-of-bounds read. A malicious server or man-in-the-middle attacker can send invalid data to trigger this vulnerability...

CVE-2016-2366

A denial of service vulnerability 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 server or an attacker who intercepts the network traffic can send invalid data to trigger this...

CVE-2016-2369

A NULL pointer dereference vulnerability exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT data sent via the server could potentially result in a denial of service vulnerability. A malicious server can send a packet starting with a NULL byte triggering the vulnerabilit...

CVE-2016-2380

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...