Skip to main content
Mallory
CriticalVulnerability

CVE-2005-2103: Buffer overflow in Gaim AIM/ICQ away message substitution handling

Published Aug 16, 2005 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS16.1%97th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Gaim Project
IdentifiersCVE-2005-2103CWE-131 · Incorrect Calculation of Buffer Size

CVE-2005-2103 is a buffer overflow vulnerability in the AIM and ICQ module of Gaim before version 1.5.0. The flaw is triggered when the client processes an away message containing a large number of AIM substitution strings such as format-style tokens used during message expansion. The vulnerable code does not correctly account for the size required after substitution, resulting in an undersized buffer and subsequent memory corruption during expansion. This can cause the application to crash and may permit arbitrary code execution in the context of the user running the client.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can cause denial of service by crashing the Gaim client. Because the flaw is a memory corruption issue caused by a buffer overflow, it may also enable arbitrary code execution with the privileges of the affected user, depending on exploitability and target conditions.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by avoiding use of vulnerable Gaim versions for AIM or ICQ messaging and limiting processing of untrusted away messages from remote contacts. Defense-in-depth measures such as compiler hardening and memory protection features may reduce exploit reliability but do not eliminate the vulnerability.

Remediation

Patch, then assume compromise.

Upgrade Gaim to version 1.5.0 or later, where the vulnerability is fixed. The underlying defect should be addressed by correcting buffer size calculations for away message substitution handling and ensuring allocation accounts for worst-case expansion during token replacement.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Gaim ProjectGaimapplication
FAQ

Frequently asked questions

Is CVE-2005-2103 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2005-2103 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2005-2103?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2005-2103. 1 candidate exploit record is not yet analyzed.
Is there a patch for CVE-2005-2103?
Upgrade Gaim to version 1.5.0 or later, where the vulnerability is fixed. The underlying defect should be addressed by correcting buffer size calculations for away message substitution handling and ensuring allocation accounts for worst-case expansion during token replacement.
What products are affected by CVE-2005-2103?
Gaim Project Gaim.
How severe is CVE-2005-2103?
CVE-2005-2103 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 16.1% (97th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.