CVE-2001-0233 in the critical feed json
Buffer overflow in micq client 0.4.6 and earlier allows remote attackers to cause a denial of service, and possibly execute arbitrary comma…
published 2001-03-26 25 y ago modified 2026-06-16 4 mo ago also EUVD-2001-0233
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 14.6%
- EPSS 14.6% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB
Summary
Buffer overflow in micq client 0.4.6 and earlier allows remote attackers to cause a denial of service, and possibly execute arbitrary commands, via a long Description field.
Patch / fix
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2001-0233 updated
security flaw
-
Red Hat Powertools 6.2 Red Hat Powertools 7.0fixed: vendor fix RHSA-2001:005
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Timeline
- First public exploit (EDB-20569)
- Published
Exploit prediction
14.55% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-20569 mICQ 0.4.6 - Remote Buffer Overflow remote, 2001-01-17
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
References
-
redhat.com
/support/errata/RHSA-2001-005.html
vendor-advisory, patch
-
debian.org
/security/2001/dsa-012
vendor-advisory, patch
-
archives.neohapsis.com
/archives/bugtraq/2001-01/0395.html
mailing-list, patch, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/5962
vdb-entry
-
archives.neohapsis.com
/archives/bugtraq/2001-01/0307.html
mailing-list
Sources
- CVE List CVE-2001-0233
- NVD CVE-2001-0233
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.