CVE-2005-1655: Medium severity aol vulnerability
Published May 18, 2005
·Updated
AOL Instant Messenger 5.5.x and earlier allows remote attackers to cause a denial of service (client crash) via an invalid smiley icon location in the sml parameter of a font tag.
Affected Software
36 affected components
AOL Instant Messenger=2.1.1236
AOL Instant Messenger=1.2
AOL Instant Messenger=4.2
AOL Instant Messenger=4.0
AOL Instant Messenger=5.0.2938
AOL Instant Messenger=5.5.3595
AOL Instant Messenger=3.5.1856
AOL Instant Messenger=4.8.2646
AOL Instant Messenger=4.5
AOL Instant Messenger=2.0.912
AOL Instant Messenger=4.3
AOL Instant Messenger=3.0_n
AOL Instant Messenger=2.0.996
AOL Instant Messenger=4.1.2010
AOL Instant Messenger=4.6
AOL Instant Messenger=3.0.1415
AOL Instant Messenger=3.5.1635
AOL Instant Messenger=5.9.3702
AOL Instant Messenger=5.5
AOL Instant Messenger=2.0_n
AOL Instant Messenger=4.3.2229
AOL Instant Messenger=2.5.1598
AOL Instant Messenger=4.8.2616
AOL Instant Messenger=3.0.1470
AOL Instant Messenger=3.5.1808
AOL Instant Messenger=5.1.3036
AOL Instant Messenger=4.2.1193
AOL Instant Messenger=3.5.1670
AOL Instant Messenger=4.7
AOL Instant Messenger=2.5.1366
AOL Instant Messenger=5.2.3292
AOL Instant Messenger=4.7.2480
AOL Instant Messenger=4.8.2790
AOL Instant Messenger=4.4
AOL Instant Messenger=5.5.3415_beta
AOL Instant Messenger=4.1
Event History
May 18, 2005
CVE Published
via MITRE·04:00 AM
Data Sourced
via MITRE·04:00 AM
Description
Frequently Asked Questions
1
What is the severity of CVE-2005-1655?
CVE-2005-1655 is classified as a denial of service vulnerability that can cause the AOL Instant Messenger client to crash.
2
How do I fix CVE-2005-1655?
To fix CVE-2005-1655, users should upgrade to a later version of AOL Instant Messenger that addresses this vulnerability.
3
Which versions are affected by CVE-2005-1655?
CVE-2005-1655 affects AOL Instant Messenger versions 5.5 and earlier.
4
What impact does CVE-2005-1655 have on users?
Users affected by CVE-2005-1655 may experience unexpected crashes when receiving invalid smiley icon locations.
5
Is there a workaround for CVE-2005-1655?
Currently, the best workaround for CVE-2005-1655 is to avoid using any untrusted or unknown smiley icon links until the software is updated.