dbcve.org
IcqApplication · Mirabilis

CVE-2002-0254

MEDIUM · 5.0 CVSS v2.0 Published 2002-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
ICQ 2001b Build 3659 allows remote attackers to cause a denial of service (crash) via a malformed picture that contains large height and width values, which causes the crash when viewed in Userdetails.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

ICQ 2001b Build 3659 contains a denial of service vulnerability where viewing a malformed picture file with excessively large height and width values in the Userdetails feature causes the application to crash.

MitigationUpgrade from the vulnerable ICQ 2001b Build 3659 to a current ICQ version, or discontinue use of this legacy software if no longer supported.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
IcqApplication
Affected:= 2001b_build3659

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm ICQ client is installed
    Look for ICQ executable or installation directory on the system. Check Start Menu or common installation paths like C:\Program Files\ICQ
    Affected if ICQ client is present on the system
  2. Identify the exact ICQ version
    In ICQ, go to Help > About ICQ or right-click the ICQ icon and select About. Record the exact build number displayed.
    Affected if The installed version is exactly 2001b_build3659
  3. Verify the Userdetails feature is accessible
    In the ICQ client, locate the Userdetails or User Profile feature, typically accessed by clicking on a contact's profile or avatar
    Affected if The Userdetails feature is present and functional in this ICQ version
  4. Confirm ability to view picture files in Userdetails
    Check if the Userdetails feature supports displaying profile pictures or custom images
    Affected if The Userdetails feature can display picture files and is enabled for use

The environment is affected only if ICQ version 2001b_build3659 is installed AND the Userdetails feature with picture viewing capability is used to open a malformed picture file containing excessively large height and width values.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade from the vulnerable ICQ 2001b Build 3659 to a current ICQ version, or discontinue use of this legacy software if no longer supported.

Fix this in Icq Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2002-0254 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2002-0254 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data