Skip to content
Fencer Intel
high 7.5

CVE-2016-2233 in the critical feed json

Stack-based buffer overflow in the inbound_cap_ls function in common/inbound.c in HexChat 2.10.2 allows remote IRC servers to cause a denia…

published 2017-01-18 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-3317

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
34.1%
EPSS 34.1% chance of exploitation in 30 days, percentile 98%
public exploits
1
Exploit-DB

Summary

Stack-based buffer overflow in the inbound_cap_ls function in common/inbound.c in HexChat 2.10.2 allows remote IRC servers to cause a denial of service (crash) via a large number of options in a CAP LS message.

Patch / fix

  • hexchat Debian 13, Debian 12 2.12.0-1

debian advisories DEBIAN-CVE-2016-2233

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-2016-2233 updated

hexchat: Multiple vulnerabilities

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

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

  1. First public exploit (EDB-39657)
  2. Published

Exploit prediction

34.10% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-39657 Hexchat IRC Client 2.11.0 - CAP LS Handling Buffer Overflow dos, 2016-04-04
  • packetstormsecurity.com http://packetstormsecurity.com/files/136563/Hexchat-IRC-Client-2.11.0-CAP-LS-Handling-Buffer-Overflow.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

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.