CVE-2002-1159 json
Canna 3.6 and earlier does not properly validate requests, which allows remote attackers to cause a denial of service or information leak.
published 2002-12-18 23 y ago modified 2026-06-16 4 mo ago also EUVD-2002-1146
- cvss
- 6.4
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.9%
- EPSS 1.9% chance of exploitation in 30 days, percentile 79%
- public exploits
- 0
- none known
Summary
Canna 3.6 and earlier does not properly validate requests, which allows remote attackers to cause a denial of service or information leak.
Patch / fix
- canna Debian 14, Debian 13, Debian 12 3.6p1-1
debian advisories DEBIAN-CVE-2002-1159
- debian.org/security/2003/dsa-224 advisory
- redhat.com/support/errata/RHSA-2002-246.html advisory
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-2002-1159 updated
security flaw
-
Red Hat Linux 7.1 Red Hat Linux 7.2 Red Hat Linux 7.3 Red Hat Linux 8.0fixed: vendor fix RHSA-2002:246
-
Red Hat Linux Advanced Workstation 2.1fixed: vendor fix RHSA-2002:261
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
Exploit prediction
1.90% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.4 | AV:N/AC:L/Au:N/C:P/I:N/A:P |
References
-
debian.org
/security/2003/dsa-224
vendor-advisory, patch
-
redhat.com
/support/errata/RHSA-2002-246.html
vendor-advisory, patch
-
redhat.com
/support/errata/RHSA-2002-261.html
vendor-advisory
-
redhat.com
/support/errata/RHSA-2003-115.html
vendor-advisory
-
securityfocus.com
/bid/6354
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/10832
vdb-entry
- canna.sourceforge.jp /sec/Canna-2002-01.txt
Sources
- CVE List CVE-2002-1159
- NVD CVE-2002-1159
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.