CVE-2009-2694
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 20.3% chance of exploitation in the next 30 days (EPSS). Higher than most.
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- ReservedThe CVE id was reserved by its CNA
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 20.3% in the next 30 days (EPSS).
- Severity: 10.0 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 20.3% · EPSS, next 30 days
- Weakness
- CWE-399
- Record status
- Modified
Affected
- Adium ≤ 1.3.5
- Adium 1.2.7
- Adium 1.3
- Adium 1.3.1
- Adium 1.3.2
- Adium 1.3.3
- Adium 1.3.4
- Pidgin ≤ 2.5.8
Attack profile CVSS 2.0 · 10.0
- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
Raw vector
AV:N/AC:L/Au:N/C:C/I:C/A:C
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2009-2694.md and follow it. Check whether this project is affected by CVE-2009-2694. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- http://developer.pidgin.im/viewmtn/revision/info/6f7343166c673bf0496ecb1afec9b633c1d54a0e
- http://secunia.com/advisories/36384
- http://secunia.com/advisories/36392
- http://secunia.com/advisories/36401
- http://www.debian.org/security/2009/dsa-1870
- http://www.pidgin.im/news/security/?id=34
- http://www.vupen.com/english/advisories/2009/2303
- https://rhn.redhat.com/errata/RHSA-2009-1218.html
- http://developer.pidgin.im/viewmtn/revision/info/6f7343166c673bf0496ecb1afec9b633c1d54a0e
- http://secunia.com/advisories/36384
References
- http://developer.pidgin.im/viewmtn/revision/info/6f7343166c673bf0496ecb1afec9b633c1d54a0e
- http://developer.pidgin.im/wiki/ChangeLog
- http://secunia.com/advisories/36384
- http://secunia.com/advisories/36392
- http://secunia.com/advisories/36401
- http://secunia.com/advisories/36402
- http://secunia.com/advisories/36708
- http://secunia.com/advisories/37071
- http://sunsolve.sun.com/search/document.do?assetkey=1-66-266908-1
- http://www.coresecurity.com/content/libpurple-arbitrary-write
- http://www.debian.org/security/2009/dsa-1870
- http://www.exploit-db.com/exploits/9615
- http://www.pidgin.im/news/security/?id=34
- http://www.vupen.com/english/advisories/2009/2303
- http://www.vupen.com/english/advisories/2009/2663
- https://bugzilla.redhat.com/show_bug.cgi?id=514957
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A10319
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A6320
- https://rhn.redhat.com/errata/RHSA-2009-1218.html
- http://developer.pidgin.im/viewmtn/revision/info/6f7343166c673bf0496ecb1afec9b633c1d54a0e
- http://developer.pidgin.im/wiki/ChangeLog
- http://secunia.com/advisories/36384
- http://secunia.com/advisories/36392
- http://secunia.com/advisories/36401
- http://secunia.com/advisories/36402