Skip to main content

Pidgin CVE-2013-6490

CRITICAL
Buffer Overflow (CWE-119)
2014-02-06 secalert@redhat.com
10.0
CVSS 2.0 · NVD
View

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, buffer size validation
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Impact

CVSS score of 10.0 (CRITICAL). Attack characteristics: network attack vector, low complexity. EPSS exploitation probability: 38.98%.

Exploit ScenarioDerived

A remote attacker could corrupt memory to execute arbitrary code or crash the application by sending crafted requests to the affected application.

Emergency Immediate action required. Why: CRITICAL + EPSS > 30%, no patch available.
No patch listed yet 39.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAI

The SIMPLE protocol functionality in Pidgin before 2.10.8 allows remote attackers to have an unspecified impact via a negative Content-Length header, which triggers a buffer overflow. Rated critical severity (CVSS 10.0), this vulnerability is remotely exploitable, low attack complexity. Epss exploitation probability 39.0% and no vendor patch available.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Use memory-safe languages or bounds-checking. Enable ASLR, DEP/NX, stack canaries. Use safe string functions.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This vulnerability is classified as Buffer Overflow (CWE-119), which allows attackers to corrupt memory to execute arbitrary code or crash the application. The SIMPLE protocol functionality in Pidgin before 2.10.8 allows remote attackers to have an unspecified impact via a negative Content-Length header, which triggers a buffer overflow. Affected products include: Pidgin. Version information: before 2.10.8.

Know when Pidgin gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 10.0 CRITICAL
AV:N/AC:L/Au:N/C:C/I:C/A:C

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Confidentiality
C
Integrity
C
Availability
C

DescriptionCVE.org

The SIMPLE protocol functionality in Pidgin before 2.10.8 allows remote attackers to have an unspecified impact via a negative Content-Length header, which triggers a buffer overflow.

Threat Intelligence Overview

EPSS Score
39.0%
Top 3% exploitable
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 39.0%
Patch available No
Active threat No
Deciding rule
CRITICAL + EPSS > 30%, no patch available
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

89
Low Medium High Critical
KEV: 0
EPSS: +39
CVSS: +50
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Affected Products (CPE)CVE.org

cpe:2.3:a:pidgin:pidgin:*:*:*:*:*:*:*:*
cpe:2.3:a:pidgin:pidgin:2.0.0:*:*:*:*:*:*:*
cpe:2.3:a:pidgin:pidgin:2.0.1:*:*:*:*:*:*:*
cpe:2.3:a:pidgin:pidgin:2.0.2:*:*:*:*:*:*:*
cpe:2.3:a:pidgin:pidgin:2.1.0:*:*:*:*:*:*:*
cpe:2.3:a:pidgin:pidgin:2.1.1:*:*:*:*:*:*:*
cpe:2.3:a:pidgin:pidgin:2.2.0:*:*:*:*:*:*:*
cpe:2.3:a:pidgin:pidgin:2.2.1:*:*:*:*:*:*:*
cpe:2.3:a:pidgin:pidgin:2.2.2:*:*:*:*:*:*:*
cpe:2.3:a:pidgin:pidgin:2.3.0:*:*:*:*:*:*:*
cpe:2.3:a:pidgin:pidgin:2.3.1:*:*:*:*:*:*:*
cpe:2.3:a:pidgin:pidgin:2.4.0:*:*:*:*:*:*:*
cpe:2.3:a:pidgin:pidgin:2.4.1:*:*:*:*:*:*:*
cpe:2.3:a:pidgin:pidgin:2.4.2:*:*:*:*:*:*:*
cpe:2.3:a:pidgin:pidgin:2.4.3:*:*:*:*:*:*:*
cpe:2.3:a:pidgin:pidgin:2.5.0:*:*:*:*:*:*:*
cpe:2.3:a:pidgin:pidgin:2.5.1:*:*:*:*:*:*:*
cpe:2.3:a:pidgin:pidgin:2.5.2:*:*:*:*:*:*:*
cpe:2.3:a:pidgin:pidgin:2.5.3:*:*:*:*:*:*:*
cpe:2.3:a:pidgin:pidgin:2.5.4:*:*:*:*:*:*:*
+ 33 more

More in Pidgin

View all
CVE-2012-3374 HIGH POC
7.5 Jul 07

Buffer overflow in markup.c in the MXit protocol plugin in libpurple in Pidgin before 2.10.5 allows remote attackers to

CVE-2019-25544 MEDIUM POC
6.9 Mar 21

Pidgin 2.13.0 contains a denial of service vulnerability that allows local attackers to crash the application by providi

CVE-2013-6486 CRITICAL
9.3 Feb 06

gtkutils.c in Pidgin before 2.10.8 on Windows allows user-assisted remote attackers to execute arbitrary programs via a

CVE-2016-2376 HIGH
8.1 Jan 06

A buffer overflow vulnerability exists in the handling of the MXIT protocol in Pidgin. Rated high severity (CVSS 8.1), t

CVE-2016-2368 HIGH
8.1 Jan 06

Multiple memory corruption vulnerabilities exist in the handling of the MXIT protocol in Pidgin. Rated high severity (CV

CVE-2012-2318 MEDIUM POC
5.0 Jul 03

msg.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.4 does not properly handle crafted characters, which

CVE-2016-2379 HIGH
8.8 Mar 29

The Mxit protocol uses weak encryption when encrypting user passwords, which might allow attackers to (1) decrypt hashed

CVE-2016-2371 HIGH
8.1 Jan 06

An out-of-bounds write vulnerability exists in the handling of the MXIT protocol in Pidgin. Rated high severity (CVSS 8.

CVE-2016-2378 HIGH
8.1 Jan 06

A buffer overflow vulnerability exists in the handling of the MXIT protocol Pidgin. Rated high severity (CVSS 8.1), this

CVE-2016-2377 HIGH
8.1 Jan 06

A buffer overflow vulnerability exists in the handling of the MXIT protocol in Pidgin. Rated high severity (CVSS 8.1), t

CVE-2016-2374 HIGH
8.1 Jan 06

An exploitable memory corruption vulnerability exists in the handling of the MXIT protocol in Pidgin. Rated high severit

CVE-2013-6487 HIGH
7.5 Feb 06

Integer overflow in libpurple/protocols/gg/lib/http.c in the Gadu-Gadu (gg) parser in Pidgin before 2.10.8 allows remote

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy