Skip to content
Noroxi
CVE-2009-2694· NVD / CVE Program· CNA mitre

The 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

Noroxi assessment

Priority: Plan (action score 46/100)

  • Public proof-of-concept code exists (Exploit-DB); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 20.2% (FIRST EPSS); higher than 97.4% of all records.
  • No special conditions are required; it is repeatable.
  • Fixed version: pidgin (Debian:12) 2.5.9-1; pidgin (Debian:5.0) 2.4.3-4lenny3; pidgin (Red Hat:enterprise_linux:3::as) 0:1.5.1-4.el3.

Add it to your regular patch cycle. Upgrade to pidgin (Debian:12) 2.5.9-1; pidgin (Debian:5.0) 2.4.3-4lenny3; pidgin (Red Hat:enterprise_linux:3::as) 0:1.5.1-4.el3 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 msn_slplink_process_msg function in libpurple/protocols/msn/slplink.c in libpurple, as used in Pidgin (formerly Gaim) before 2.5.9 and Adium 1.3.5 and earlier, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) by sending multiple crafted SLP (aka MSNSLP) messages to trigger an overwrite of an arbitrary memory location. NOTE: this issue reportedly exists because of an incomplete fix for CVE-2009-1376.

CriticalCVSS 10.0 · v2.0—Proof of concept Fix available
Published
Aug 21, 2009
Updated
Jun 16, 2026
EPSS
20.2% · 97th percentile

Report tools

JSON

Action score

46

Plan

Add it to your regular patch cycle.

CVSS
40 / 40 · 10.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
6 / 30 · 20.2%

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.

Follow CVE-2009-2694

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for pidgin records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

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

VendorProduct
pidginpidgin
adiumadium

Affected versions

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

  • adium adiumup to 1.3.5 inclusive
  • adium adium1.2.7
  • adium adium1.3
  • adium adium1.3.1
  • adium adium1.3.2
  • adium adium1.3.3
  • adium adium1.3.4
  • pidgin pidginup to 2.5.8 inclusive
  • pidgin pidgin2.0.0
  • pidgin pidgin2.0.1
  • pidgin pidgin2.0.2
  • pidgin pidgin2.1.0
  • pidgin pidgin2.1.1
  • 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.5.9-12.5.9-1
Debian:5.0pidginbefore 2.4.3-4lenny32.4.3-4lenny3
Red Hat:enterprise_linux:3::aspidginbefore 0:1.5.1-4.el30:1.5.1-4.el3
Red Hat:enterprise_linux:3::aspidgin-debuginfobefore 0:1.5.1-4.el30:1.5.1-4.el3
Red Hat:enterprise_linux:4::asfinchbefore 0:2.5.9-1.el40:2.5.9-1.el4
Red Hat:enterprise_linux:4::asfinch-develbefore 0:2.5.9-1.el40:2.5.9-1.el4
Red Hat:enterprise_linux:4::aslibpurplebefore 0:2.5.9-1.el40:2.5.9-1.el4
Red Hat:enterprise_linux:4::aslibpurple-develbefore 0:2.5.9-1.el40:2.5.9-1.el4
Red Hat:enterprise_linux:4::aslibpurple-perlbefore 0:2.5.9-1.el40:2.5.9-1.el4
Red Hat:enterprise_linux:4::aslibpurple-tclbefore 0:2.5.9-1.el40:2.5.9-1.el4
Red Hat:enterprise_linux:4::aspidginbefore 0:2.5.9-1.el40:2.5.9-1.el4
Red Hat:enterprise_linux:4::aspidgin-debuginfobefore 0:2.5.9-1.el40:2.5.9-1.el4
Red Hat:enterprise_linux:4::aspidgin-develbefore 0:2.5.9-1.el40:2.5.9-1.el4
Red Hat:enterprise_linux:4::aspidgin-perlbefore 0:2.5.9-1.el40:2.5.9-1.el4
Red Hat:enterprise_linux:5::clientfinchbefore 0:2.5.9-1.el50:2.5.9-1.el5
Red Hat:enterprise_linux:5::clientlibpurplebefore 0:2.5.9-1.el50:2.5.9-1.el5
Red Hat:enterprise_linux:5::clientlibpurple-perlbefore 0:2.5.9-1.el50:2.5.9-1.el5
Red Hat:enterprise_linux:5::clientlibpurple-tclbefore 0:2.5.9-1.el50:2.5.9-1.el5
Red Hat:enterprise_linux:5::clientpidgin-perlbefore 0:2.5.9-1.el50:2.5.9-1.el5
Red Hat:enterprise_linux:5::client_workstationfinch-develbefore 0:2.5.9-1.el50:2.5.9-1.el5
Red Hat:enterprise_linux:5::client_workstationlibpurple-develbefore 0:2.5.9-1.el50:2.5.9-1.el5
Red Hat:enterprise_linux:5::client_workstationpidginbefore 0:2.5.9-1.el50:2.5.9-1.el5
Red Hat:enterprise_linux:5::client_workstationpidgin-debuginfobefore 0:2.5.9-1.el50:2.5.9-1.el5
Red Hat:enterprise_linux:5::client_workstationpidgin-develbefore 0:2.5.9-1.el50:2.5.9-1.el5

Same product

pidgin: all records

Other highest-scoring records for the same primary product.

  • CVE-2013-6490The SIMPLE protocol functionality in Pidgin before 2.10.8 allows remote attackers to have an unspecified impact via a negative Content-Lengt
    44Plan
  • 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

Published before and after this one in the same product

  • ← EarlierCVE-2009-1375May 26, 2009 · The PurpleCircBuffer implementation in Pidgin (formerly Gaim) before 2.5.6 does not properly maintain a certain buffer, which allows remote
    21Monitor
  • ← EarlierCVE-2009-1889Jul 1, 2009 · The OSCAR protocol implementation in Pidgin before 2.5.8 misinterprets the ICQWebMessage message type as the ICQSMS message type, which allo
    21Monitor
  • Later →CVE-2009-3025Aug 31, 2009 · Unspecified vulnerability in Pidgin 2.6.0 allows remote attackers to cause a denial of service (crash) via a link in a Yahoo IM.
    18Monitor

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.5.9-1 · Debian:12Package registry (OSV)
red hat:finch0:2.5.9-1.el4 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:finch-devel0:2.5.9-1.el4 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:libpurple0:2.5.9-1.el4 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:libpurple-devel0:2.5.9-1.el4 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:libpurple-perl0:2.5.9-1.el4 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:libpurple-tcl0:2.5.9-1.el4 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:pidgin0:1.5.1-4.el3 · Red Hat:enterprise_linux:3::asPackage registry (OSV)
red hat:pidgin-debuginfo0:1.5.1-4.el3 · Red Hat:enterprise_linux:3::asPackage registry (OSV)
red hat:pidgin-devel0:2.5.9-1.el4 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:pidgin-perl0:2.5.9-1.el4 · Red Hat:enterprise_linux:4::asPackage 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

  • Exploit-DB entry ×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
Exploit-DB entryremote2009-09-09

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+19 d
  3. TodayOct 22, 2026+6271 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.

No commit or PR link among the references.

Credits

All researchers

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

Weakness class (CWE)

CWE-399 · Resource Management Errors

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

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

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

References

Show all references (17 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records