Skip to content
Noroxi
CVE-2013-6490· NVD / CVE Program· CNA redhat

The SIMPLE protocol functionality in Pidgin before 2.10.8 allows remote attackers to have an unspecified impact via a negative Content-Lengt

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.

CriticalCVSS 10.0 · v2.0—Proof of concept Fix available
Published
Feb 6, 2014
Updated
Jun 16, 2026
EPSS
14.8% · 97th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

44

Plan

Add it to your regular patch cycle.

CVSS
40 / 40 · 10.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
4 / 30 · 14.8%

Affected systems

VendorProduct
pidginpidgin

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • pidgin pidginup to 2.10.7 inclusive
  • pidgin pidgin2.0.0
  • pidgin pidgin2.0.1
  • pidgin pidgin2.0.2
  • pidgin pidgin2.1.0
  • pidgin pidgin2.1.1
  • pidgin pidgin2.10.0
  • pidgin pidgin2.10.1
  • pidgin pidgin2.10.2
  • pidgin pidgin2.10.3
  • pidgin pidgin2.10.4
  • pidgin pidgin2.10.5
  • pidgin pidgin2.10.6
  • pidgin pidgin2.2.0
  • pidgin pidgin2.2.1
  • pidgin pidgin2.2.2
  • pidgin pidgin2.3.0
  • pidgin pidgin2.3.1
  • pidgin pidgin2.4.0
  • pidgin pidgin2.4.1

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12pidginbefore 2.10.8-12.10.8-1
Debian:6.0pidginbefore 2.7.3-1+squeeze42.7.3-1+squeeze4
Debian:7pidginbefore 2.10.9-1~deb7u12.10.9-1~deb7u1
Red Hat:enterprise_linux:5::clientfinchbefore 0:2.6.6-32.el50:2.6.6-32.el5
Red Hat:enterprise_linux:5::clientlibpurplebefore 0:2.6.6-32.el50:2.6.6-32.el5
Red Hat:enterprise_linux:5::clientlibpurple-perlbefore 0:2.6.6-32.el50:2.6.6-32.el5
Red Hat:enterprise_linux:5::clientlibpurple-tclbefore 0:2.6.6-32.el50:2.6.6-32.el5
Red Hat:enterprise_linux:5::clientpidginbefore 0:2.6.6-32.el50:2.6.6-32.el5
Red Hat:enterprise_linux:5::clientpidgin-debuginfobefore 0:2.6.6-32.el50:2.6.6-32.el5
Red Hat:enterprise_linux:5::clientpidgin-perlbefore 0:2.6.6-32.el50:2.6.6-32.el5
Red Hat:enterprise_linux:5::client_workstationfinch-develbefore 0:2.6.6-32.el50:2.6.6-32.el5
Red Hat:enterprise_linux:5::client_workstationlibpurple-develbefore 0:2.6.6-32.el50:2.6.6-32.el5
Red Hat:enterprise_linux:5::client_workstationpidgin-develbefore 0:2.6.6-32.el50:2.6.6-32.el5
Red Hat:enterprise_linux:6::clientfinchbefore 0:2.7.9-27.el60:2.7.9-27.el6
Red Hat:enterprise_linux:6::clientfinch-develbefore 0:2.7.9-27.el60:2.7.9-27.el6
Red Hat:enterprise_linux:6::clientlibpurplebefore 0:2.7.9-27.el60:2.7.9-27.el6
Red Hat:enterprise_linux:6::clientlibpurple-develbefore 0:2.7.9-27.el60:2.7.9-27.el6
Red Hat:enterprise_linux:6::clientlibpurple-perlbefore 0:2.7.9-27.el60:2.7.9-27.el6
Red Hat:enterprise_linux:6::clientlibpurple-tclbefore 0:2.7.9-27.el60:2.7.9-27.el6
Red Hat:enterprise_linux:6::clientpidginbefore 0:2.7.9-27.el60:2.7.9-27.el6
Red Hat:enterprise_linux:6::clientpidgin-debuginfobefore 0:2.7.9-27.el60:2.7.9-27.el6
Red Hat:enterprise_linux:6::clientpidgin-develbefore 0:2.7.9-27.el60:2.7.9-27.el6
Red Hat:enterprise_linux:6::clientpidgin-docsbefore 0:2.7.9-27.el60:2.7.9-27.el6
Red Hat:enterprise_linux:6::clientpidgin-perlbefore 0:2.7.9-27.el60:2.7.9-27.el6

Other highest-scoring records for the same primary product.

  • CVE-2009-2694The msn_slplink_process_msg function in libpurple/protocols/msn/slplink.c in libpurple, as used in Pidgin (formerly Gaim) before 2.5.9 and A
    46Plan
  • CVE-2017-2640An out-of-bounds write flaw was found in the way Pidgin before 2.12.0 processed XML content.
    41Plan
  • CVE-2009-1376Multiple integer overflows in the msn_slplink_process_msg functions in the MSN protocol handler in (1) libpurple/protocols/msn/slplink.c and
    41Plan
  • CVE-2016-1000030Pidgin version <2.11.0 contains a vulnerability in X.509 Certificates imports specifically due to improper check of return values from gnutl
    40Plan
  • CVE-2013-6486gtkutils.c in Pidgin before 2.10.8 on Windows allows user-assisted remote attackers to execute arbitrary programs via a message containing a
    38Monitor
  • CVE-2011-3185gtkutils.c in Pidgin before 2.10.0 on Windows allows user-assisted remote attackers to execute arbitrary programs via a file: URL in a messa
    38Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:pidgin2.10.8-1 · Debian:12Package registry (OSV)
red hat:finch0:2.6.6-32.el5 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:finch-devel0:2.6.6-32.el5 · Red Hat:enterprise_linux:5::client_workstationPackage registry (OSV)
red hat:libpurple0:2.6.6-32.el5 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:libpurple-devel0:2.6.6-32.el5 · Red Hat:enterprise_linux:5::client_workstationPackage registry (OSV)
red hat:libpurple-perl0:2.6.6-32.el5 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:libpurple-tcl0:2.6.6-32.el5 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:pidgin0:2.6.6-32.el5 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:pidgin-debuginfo0:2.6.6-32.el5 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:pidgin-devel0:2.6.6-32.el5 · Red Hat:enterprise_linux:5::client_workstationPackage registry (OSV)
red hat:pidgin-docs0:2.7.9-27.el6 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:pidgin-perl0:2.6.6-32.el5 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02022-10-05

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+3162 d
  3. TodaySep 30, 2026+4619 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • No special conditions are required; it is repeatable.

If successful

Confidentiality
C · data can be read
Integrity
C · data or configuration can be modified
Availability
C · the service can be disrupted
Attack complexity
Low
Confidentiality impact
C
Integrity impact
C
Availability impact
C

CVSS vector

AV:N/AC:L/Au:N/C:C/I:C/A:C

nvd-primary

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records