CVE-2009-4652 json
The (1) Conn_GetCipherInfo and (2) Conn_UsesSSL functions in src/ngircd/conn.c in ngIRCd 13 and 14, when SSL/TLS support is present and sta…
published 16y ago modified 4mo ago also EUVD-2009-4617
- cvss
- 2.6
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
The (1) Conn_GetCipherInfo and (2) Conn_UsesSSL functions in src/ngircd/conn.c in ngIRCd 13 and 14, when SSL/TLS support is present and standalone mode is disabled, allow remote attackers to cause a denial of service (application crash) by sending the MOTD command from another server in the same IRC network, possibly related to an array index error.
Patch / fix
- ngircd Debian 14, Debian 13, Debian 12 15-0.1
debian advisories DEBIAN-CVE-2009-4652
Is CVE-2009-4652 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.59% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- securityfocus.com http://www.securityfocus.com/bid/37021 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 2.6 | AV:N/AC:H/Au:N/C:N/I:N/A:P |
References
-
securityfocus.com
/bid/37021
vdb-entry, exploit
-
vupen.com
/english/advisories/2009/3240
vdb-entry, vendor-advisory
-
secunia.com
/advisories/37343
third-party-advisory, vendor-advisory
-
ngircd.barton.de
/doc/NEWS
vendor-advisory
- arthur.barton.de /cgi-bin/gitweb.cgi?p=ngircd.git%3Ba=blobdiff%3Bf=src/ngircd/conn.c%3Bh=c6095a31c613bc5ca127d55b8723e15b836f1c
- ngircd.barton.de /doc/ChangeLog
- arthur.barton.de /cgi-bin/gitweb.cgi?p=ngircd.git%3Ba=commit%3Bh=627b0b713c52406e50c84bb9459e7794262920a2
-
exchange.xforce.ibmcloud.com
/vulnerabilities/54272
vdb-entry
Sources
- CVE List CVE-2009-4652
- NVD CVE-2009-4652
Fencer Intel 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.