Skip to content
Noroxi
CVE-2010-1624· NVD / CVE Program· CNA redhat

The msn_emoticon_msg function in slp.c in the MSN protocol plugin in libpurple in Pidgin before 2.7.0 allows remote authenticated users to c

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 5.5% (FIRST EPSS); higher than 92.8% of all records.
  • No special conditions are required; it is repeatable.
  • Fixed version: pidgin (Debian:12) 2.7.0-1; finch (Red Hat:enterprise_linux:4::as) 0:2.6.6-5.el4_8; finch-devel (Red Hat:enterprise_linux:4::as) 0:2.6.6-5.el4_8.

Low priority for now. Upgrade to pidgin (Debian:12) 2.7.0-1; finch (Red Hat:enterprise_linux:4::as) 0:2.6.6-5.el4_8; finch-devel (Red Hat:enterprise_linux:4::as) 0:2.6.6-5.el4_8 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_emoticon_msg function in slp.c in the MSN protocol plugin in libpurple in Pidgin before 2.7.0 allows remote authenticated users to cause a denial of service (NULL pointer dereference and application crash) via a custom emoticon in a malformed SLP message.

MediumCVSS 5.0 · v2.0—No exploit Fix available
Published
May 14, 2010
Updated
Jun 16, 2026
EPSS
5.5% · 92th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
20 / 40 · 5.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
2 / 30 · 5.5%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2010-1624

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
canonicalubuntu linux

Affected versions

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

  • canonical ubuntu linux10.04
  • canonical ubuntu linux10.10
  • canonical ubuntu linux8.04
  • canonical ubuntu linux9.10
  • pidgin pidginbefore 2.7.0

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12pidginbefore 2.7.0-12.7.0-1
Red Hat:enterprise_linux:4::asfinchbefore 0:2.6.6-5.el4_80:2.6.6-5.el4_8
Red Hat:enterprise_linux:4::asfinch-develbefore 0:2.6.6-5.el4_80:2.6.6-5.el4_8
Red Hat:enterprise_linux:4::aslibpurplebefore 0:2.6.6-5.el4_80:2.6.6-5.el4_8
Red Hat:enterprise_linux:4::aslibpurple-develbefore 0:2.6.6-5.el4_80:2.6.6-5.el4_8
Red Hat:enterprise_linux:4::aslibpurple-perlbefore 0:2.6.6-5.el4_80:2.6.6-5.el4_8
Red Hat:enterprise_linux:4::aslibpurple-tclbefore 0:2.6.6-5.el4_80:2.6.6-5.el4_8
Red Hat:enterprise_linux:4::aspidginbefore 0:2.6.6-5.el4_80:2.6.6-5.el4_8
Red Hat:enterprise_linux:4::aspidgin-debuginfobefore 0:2.6.6-5.el4_80:2.6.6-5.el4_8
Red Hat:enterprise_linux:4::aspidgin-develbefore 0:2.6.6-5.el4_80:2.6.6-5.el4_8
Red Hat:enterprise_linux:4::aspidgin-perlbefore 0:2.6.6-5.el4_80:2.6.6-5.el4_8
Red Hat:enterprise_linux:5::clientfinchbefore 0:2.6.6-5.el5_50:2.6.6-5.el5_5
Red Hat:enterprise_linux:5::clientlibpurplebefore 0:2.6.6-5.el5_50:2.6.6-5.el5_5
Red Hat:enterprise_linux:5::clientlibpurple-perlbefore 0:2.6.6-5.el5_50:2.6.6-5.el5_5
Red Hat:enterprise_linux:5::clientlibpurple-tclbefore 0:2.6.6-5.el5_50:2.6.6-5.el5_5
Red Hat:enterprise_linux:5::clientpidgin-perlbefore 0:2.6.6-5.el5_50:2.6.6-5.el5_5
Red Hat:enterprise_linux:5::client_workstationfinch-develbefore 0:2.6.6-5.el5_50:2.6.6-5.el5_5
Red Hat:enterprise_linux:5::client_workstationlibpurple-develbefore 0:2.6.6-5.el5_50:2.6.6-5.el5_5
Red Hat:enterprise_linux:5::client_workstationpidginbefore 0:2.6.6-5.el5_50:2.6.6-5.el5_5
Red Hat:enterprise_linux:5::client_workstationpidgin-debuginfobefore 0:2.6.6-5.el5_50:2.6.6-5.el5_5
Red Hat:enterprise_linux:5::client_workstationpidgin-develbefore 0:2.6.6-5.el5_50:2.6.6-5.el5_5

Same product

pidgin: all records

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

Published before and after this one in the same product

  • ← EarlierCVE-2010-0420Feb 24, 2010 · libpurple in Finch in Pidgin before 2.6.6, when an XMPP multi-user chat (MUC) room is used, does not properly parse nicknames containing <br
    18Monitor
  • ← EarlierCVE-2010-0423Feb 24, 2010 · gtkimhtml.c in Pidgin before 2.6.6 allows remote attackers to cause a denial of service (CPU consumption and application hang) by sending ma
    21Monitor
  • Later →CVE-2010-2528Jul 30, 2010 · The clientautoresp function in family_icbm.c in the oscar protocol plugin in libpurple in Pidgin before 2.7.2 allows remote authenticated us
    17Monitor

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.7.0-1 · Debian:12Package registry (OSV)
red hat:finch0:2.6.6-5.el4_8 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:finch-devel0:2.6.6-5.el4_8 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:libpurple0:2.6.6-5.el4_8 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:libpurple-devel0:2.6.6-5.el4_8 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:libpurple-perl0:2.6.6-5.el4_8 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:libpurple-tcl0:2.6.6-5.el4_8 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:pidgin0:2.6.6-5.el4_8 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:pidgin-debuginfo0:2.6.6-5.el4_8 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:pidgin-devel0:2.6.6-5.el4_8 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:pidgin-perl0:2.6.6-5.el4_8 · Red Hat:enterprise_linux:4::asPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

No dated events beyond publication.

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.

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
none
Integrity
none
Availability
P · the service can be disrupted
Attack complexity
Low
Confidentiality impact
None
Integrity impact
None
Availability impact
P

Weakness class (CWE)

CWE-20 · Improper Input Validation

CVSS vector

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

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.

Change log

  1. Fix✗ → ✓

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

References

Show all references (13 more)

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

All records