236 matches found
CVE-2016-2378
A buffer overflow vulnerability exists in the handling of the MXIT protocol Pidgin. Specially crafted data sent via the server could potentially result in a buffer overflow, potentially resulting in memory corruption. A malicious server or an unfiltered malicious user can send negative length...
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-2370
CVE-2016-2370 (Pidgin) affects the MXIT protocol handling in Pidgin. The vulnerability arises from processing specially crafted MXIT data from a server, potentially causing an out-of-bounds read and enabling a crash or memory disclosure. The discovery is based on the CVE entry and associated refe...
CVE-2016-2371
CVE-2016-2371 describes an out-of-bounds write in the MXIT protocol handling in Pidgin , causing memory corruption that could lead to code execution. The linked connected documents (including EulerOS/Nessus entries) corroborate this issue as part of a broader set of MXIT-related vulnerabilities i...
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-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-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-2376
CVE-2016-2376 — Pidgin MXIT buffer overflow : A vulnerability in the MXIT protocol handling in Pidgin could be triggered by specially crafted MXIT data from a server, potentially causing arbitrary code execution due to a buffer overflow. The initial description notes an invalid packet size as the...
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...
CVE-2016-2367
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 can send an invalid size for an avatar which will trigger an out-of-bounds...
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-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-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-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-2378
A buffer overflow vulnerability exists in the handling of the MXIT protocol Pidgin. Specially crafted data sent via the server could potentially result in a buffer overflow, potentially resulting in memory corruption. A malicious server or an unfiltered malicious user can send negative length...
CVE-2016-2374
The CVE-2016-2374 entry affects Pidgin's MXIT protocol handling. The vulnerability is an exploitable memory corruption in the MXIT MultiMX message handling, where specially crafted server messages can trigger an out-of-bounds write, leading to memory disclosure and potential code execution. Affec...
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-2376
A buffer overflow vulnerability exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT data sent from the server could potentially result in arbitrary code execution. A malicious server or an attacker who intercepts the network traffic can send an invalid size for a packet...
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-2380
CVE-2016-2380 affects Pidgin via an information leak in MXIT protocol handling. Specially crafted MXIT data could trigger an out-of-bounds read when a user enters a string that is mis-converted, per multiple connected advisories (e.g., Nessus/Red Hat EulerOS entries). The vulnerability is limited...