search menu icon-carat-right cmu-wordmark

CERT Coordination Center

Gaim vulnerable to HTML processing denial of service

Vulnerability Note VU#523888

Original Release Date: 2005-02-21 | Last Revised: 2005-02-21

Overview

Gaim contains a flaw in HTML processing that may result in an invalid memory access and denial of service condition.

Description

From the Gaim project:

Gaim is a multi-protocol instant messaging (IM) client for Linux, BSD, MacOS X, and Windows. It is compatible with AIM and ICQ (Oscar protocol), MSN Messenger, Yahoo!, IRC, Jabber, Gadu-Gadu, SILC, GroupWise Messenger, and Zephyr networks

Gaim is susceptible to receiving a malformed HTML message which may result in an invalid memory access.

Impact

A remote attacker can cause Gaim to crash, causing a denial of service condition.

Solution

Apply an update
This flaw has been fixed in Gaim 1.1.3, along with other potential security vulnerabilities. All users may download an update at the Gaim Downloads page.

As a best practice and potential workaround, users should not accept unexpected messages from unknown sources.

Vendor Information

523888
 
Affected   Unknown   Unaffected

Gaim

Updated:  February 21, 2005

Status

  Vulnerable

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The Gaim project has issued a Gaim Vulnerability note regarding this flaw.

If you have feedback, comments, or additional information about this vulnerability, please send us email.


CVSS Metrics

Group Score Vector
Base N/A N/A
Temporal N/A N/A
Environmental N/A

References

Acknowledgements

Thanks to the Gaim project for reporting this vulnerability.

This document was written by Ken MacInnis based primarily on information from the Gaim project.

Other Information

CVE IDs: CVE-2005-0473
Severity Metric: 1.28
Date Public: 2005-02-17
Date First Published: 2005-02-21
Date Last Updated: 2005-02-21 21:41 UTC
Document Revision: 8

Sponsored by the Department of Homeland Security Office of Cybersecurity and Communications.