CVE-2013-6490: The SIMPLE protocol functionality in Pidgin before 2.10.8 allows remote attackers to have an unspecified impact via a negative…
Noroxi assessment
Priority: Plan (action score 44/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 14.8% (FIRST EPSS); higher than 96.7% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: pidgin (Debian:12) 2.10.8-1; pidgin (Debian:6.0) 2.7.3-1+squeeze4; pidgin (Debian:7) 2.10.9-1~deb7u1.
Add it to your regular patch cycle. Upgrade to pidgin (Debian:12) 2.10.8-1; pidgin (Debian:6.0) 2.7.3-1+squeeze4; pidgin (Debian:7) 2.10.9-1~deb7u1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Feb 6, 2014
- Updated
- Jun 16, 2026
- EPSS
- 14.8% · 96th percentile
- CWE
- CWE-119
Report tools
Action score
44
Add it to your regular patch cycle.
- CVSS
- 40 / 40 · 10.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 4 / 30 · 14.8%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| pidgin | pidgin | cpe:2.3:a:pidgin:pidgin |
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
+12 more rows
- 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.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | pidgin | before 2.10.8-1 | 2.10.8-1 |
| Debian:6.0 | pidgin | before 2.7.3-1+squeeze4 | 2.7.3-1+squeeze4 |
| Debian:7 | pidgin | before 2.10.9-1~deb7u1 | 2.10.9-1~deb7u1 |
| Red Hat:enterprise_linux:5::client | finch | before 0:2.6.6-32.el5 | 0:2.6.6-32.el5 |
| Red Hat:enterprise_linux:5::client | libpurple | before 0:2.6.6-32.el5 | 0:2.6.6-32.el5 |
| Red Hat:enterprise_linux:5::client | libpurple-perl | before 0:2.6.6-32.el5 | 0:2.6.6-32.el5 |
| Red Hat:enterprise_linux:5::client | libpurple-tcl | before 0:2.6.6-32.el5 | 0:2.6.6-32.el5 |
| Red Hat:enterprise_linux:5::client | pidgin | before 0:2.6.6-32.el5 | 0:2.6.6-32.el5 |
| Red Hat:enterprise_linux:5::client | pidgin-debuginfo | before 0:2.6.6-32.el5 | 0:2.6.6-32.el5 |
| Red Hat:enterprise_linux:5::client | pidgin-perl | before 0:2.6.6-32.el5 | 0:2.6.6-32.el5 |
| Red Hat:enterprise_linux:5::client_workstation | finch-devel | before 0:2.6.6-32.el5 | 0:2.6.6-32.el5 |
| Red Hat:enterprise_linux:5::client_workstation | libpurple-devel | before 0:2.6.6-32.el5 | 0:2.6.6-32.el5 |
| Red Hat:enterprise_linux:5::client_workstation | pidgin-devel | before 0:2.6.6-32.el5 | 0:2.6.6-32.el5 |
| Red Hat:enterprise_linux:6::client | finch | before 0:2.7.9-27.el6 | 0:2.7.9-27.el6 |
| Red Hat:enterprise_linux:6::client | finch-devel | before 0:2.7.9-27.el6 | 0:2.7.9-27.el6 |
| Red Hat:enterprise_linux:6::client | libpurple | before 0:2.7.9-27.el6 | 0:2.7.9-27.el6 |
| Red Hat:enterprise_linux:6::client | libpurple-devel | before 0:2.7.9-27.el6 | 0:2.7.9-27.el6 |
| Red Hat:enterprise_linux:6::client | libpurple-perl | before 0:2.7.9-27.el6 | 0:2.7.9-27.el6 |
| Red Hat:enterprise_linux:6::client | libpurple-tcl | before 0:2.7.9-27.el6 | 0:2.7.9-27.el6 |
| Red Hat:enterprise_linux:6::client | pidgin | before 0:2.7.9-27.el6 | 0:2.7.9-27.el6 |
| Red Hat:enterprise_linux:6::client | pidgin-debuginfo | before 0:2.7.9-27.el6 | 0:2.7.9-27.el6 |
| Red Hat:enterprise_linux:6::client | pidgin-devel | before 0:2.7.9-27.el6 | 0:2.7.9-27.el6 |
| Red Hat:enterprise_linux:6::client | pidgin-docs | before 0:2.7.9-27.el6 | 0:2.7.9-27.el6 |
| Red Hat:enterprise_linux:6::client | pidgin-perl | before 0:2.7.9-27.el6 | 0:2.7.9-27.el6 |
Same product
pidgin: all recordsOther 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…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…41Plan
Published before and after this one in the same product
- ← EarlierCVE-2013-6487Feb 6, 2014 · Integer overflow in libpurple/protocols/gg/lib/http.c in the Gadu-Gadu (gg) parser in Pidgin before 2.10.8 allows remote attackers to have…32Monitor
- ← EarlierCVE-2013-6489Feb 6, 2014 · Integer signedness error in the MXit functionality in Pidgin before 2.10.8 allows remote attackers to cause a denial of service…22Monitor
- Later →CVE-2014-3694Oct 29, 2014 · The (1) bundled GnuTLS SSL/TLS plugin and the (2) bundled OpenSSL SSL/TLS plugin in libpurple in Pidgin before 2.10.10 do not properly…26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:pidgin | 2.10.8-1 · Debian:12 | Package registry (OSV) |
| red hat:finch | 0:2.6.6-32.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:finch-devel | 0:2.6.6-32.el5 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| red hat:libpurple | 0:2.6.6-32.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:libpurple-devel | 0:2.6.6-32.el5 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| red hat:libpurple-perl | 0:2.6.6-32.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:libpurple-tcl | 0:2.6.6-32.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:pidgin | 0:2.6.6-32.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:pidgin-debuginfo | 0:2.6.6-32.el5 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:pidgin-devel | 0:2.6.6-32.el5 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| red hat:pidgin-docs | 0:2.7.9-27.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:pidgin-perl | 0:2.6.6-32.el5 · Red Hat:enterprise_linux:5::client | Package 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.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2022-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.
- Published
- First PoC+3162 d
- TodayNov 16, 2026+4666 d
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
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
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
AV:N/AC:L/Au:N/C:C/I:C/A:C
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.