Skip to content
Noroxi
NVD / CVE Program· CNA redhat

CVE-2011-4939: The pidgin_conv_chat_rename_user function in gtkconv.c in Pidgin before 2.10.2 allows remote attackers to cause a denial of service (NULL…

MediumCVSS 6.4 · v2.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 26/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: 3.3% (FIRST EPSS); higher than 88.9% of all records.
  • No special conditions are required; it is repeatable.
  • Fixed version: pidgin (Debian:12) 2.10.2-1.

Low priority for now. Upgrade to pidgin (Debian:12) 2.10.2-1 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 pidgin_conv_chat_rename_user function in gtkconv.c in Pidgin before 2.10.2 allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) by changing a nickname while in an XMPP chat room.

Published
Mar 15, 2012
Updated
Jun 16, 2026
EPSS
3.3% · 88th percentile

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
25 / 40 · 6.4 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 3.3%

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

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE 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, at most 30 a day (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
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

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.1 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.2.0
+12 more rows
  • pidgin pidgin2.2.1
  • pidgin pidgin2.2.2
  • pidgin pidgin2.3.0
  • pidgin pidgin2.3.1
  • pidgin pidgin2.4.0
  • pidgin pidgin2.4.1
  • pidgin pidgin2.4.2
  • pidgin pidgin2.4.3
  • pidgin pidgin2.5.0
  • pidgin pidgin2.5.1
  • pidgin pidgin2.5.2
  • pidgin pidgin2.5.3

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12pidginbefore 2.10.2-12.10.2-1

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…
    46Plan
  • CVE-2013-6490The SIMPLE protocol functionality in Pidgin before 2.10.8 allows remote attackers to have an unspecified impact via a negative…
    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-2011-4603Dec 16, 2011 · The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected…
    21Monitor
  • ← EarlierCVE-2011-4601Dec 24, 2011 · family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on…
    21Monitor
  • Later →CVE-2012-1178Mar 15, 2012 · The msn_oim_report_to_user function in oim.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.2 allows remote servers to cause…
    21Monitor

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.2-1 · Debian:12Package 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.

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

Weakness class (CWE)

CWE-264 · Permissions, Privileges, and Access Controls

CVSS vector

AV:N/AC:L/Au:N/C:N/I:P/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.

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

References

Show all references (5 more)

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

All records