CVE-2008-1227 json
Stack-based buffer overflow in the silc_fingerprint function in lib/silcutil/silcutil.c in Secure Internet Live Conferencing (SILC) Toolkit…
published 2008-03-10 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-1236
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.3%
- EPSS 4.3% chance of exploitation in 30 days, percentile 91%
- public exploits
- 0
- none known
Summary
Stack-based buffer overflow in the silc_fingerprint function in lib/silcutil/silcutil.c in Secure Internet Live Conferencing (SILC) Toolkit 1.1.5, and unspecified earlier versions, allows remote attackers to cause a denial of service (crash) or possibly execute arbitrary code via long input data. NOTE: some of these details are obtained from third party information.
Patch / fix
Exploit prediction
4.32% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
securityfocus.com
/bid/28101
vdb-entry, patch
-
security.gentoo.org
/glsa/glsa-200804-27.xml
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2008-03/msg00004.html
vendor-advisory
-
mandriva.com
/security/advisories?name=MDVSA-2008:158
vendor-advisory
-
secunia.com
/advisories/29174
third-party-advisory, vendor-advisory
- silcnet.org /docs/changelog/SILC%20Toolkit%201.1.6
-
exchange.xforce.ibmcloud.com
/vulnerabilities/41012
vdb-entry
- bugzilla.redhat.com /show_bug.cgi?id=372021
-
vupen.com
/english/advisories/2008/0769
vdb-entry
-
secunia.com
/advisories/29946
third-party-advisory
-
secunia.com
/advisories/29323
third-party-advisory
Sources
- CVE List CVE-2008-1227
- NVD CVE-2008-1227
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.