CVE-2001-0367
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 · uneditedMirabilis ICQ WebFront Plug-in ICQ2000b Build 3278 allows a remote attacker to create a denial of service via HTTP URL requests containing a large number of % characters.
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 confidenceMirabilis ICQ WebFront Plug-in ICQ2000b Build 3278 contains a denial-of-service vulnerability where malformed HTTP URL requests containing an excessive number of % characters cause the service to become unavailable. The % character triggers URL-decoding processing, and a large quantity of these characters likely causes resource exhaustion or crashes due to improper handling during parsing.
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= 2000.0b_build3278CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify ICQ installationCheck if Mirabilis ICQ is installed on the system by searching for ICQ executable files or checking installed programs in system settingsAffected if ICQ is not installed, the system is not affected by this vulnerability
-
Identify ICQ versionLocate ICQ version information through the program's About dialog, installation directory, or Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or HKCU\SOFTWARE\MirabilisAffected if The installed version is exactly 2000.0b_build3278, indicating the vulnerable build
-
Confirm WebFront component presenceCheck for the ICQ WebFront plug-in files in the ICQ installation directory, typically named WebFront or similar HTTP-handling componentsAffected if The WebFront plug-in component is present and installed alongside ICQ 2000.0b Build 3278
-
Check WebFront network exposureExamine if the ICQ WebFront service is running and listening on HTTP ports by using netstat or by reviewing configured servicesAffected if The WebFront component is actively running and accessible over the network, making it exploitable via malformed HTTP requests
A system is affected only if it has ICQ 2000.0b Build 3278 with the WebFront plug-in installed and running, exposing an HTTP service that can receive the malformed URL requests.
Generated from the published advisory. Verify against your own configuration.
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 dataPrimary remediation is to update the ICQ WebFront Plug-in to a patched version if available, or remove/disable the plugin if unused. Network-level filtering (WAF or IPS) can block requests with abnormally high % character density as a temporary mitigation.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2001-0367 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2001-0367 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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