Skip to content
Fencer Intel
critical 9.8

CVE-2019-15717 json

Irssi 1.2.x before 1.2.2 has a use-after-free if the IRC server sends a double CAP.

published 7y ago modified 4mo ago also EUVD-2019-6653

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.5%
EPSS 2.5% chance of exploitation in 30 days, percentile 84%
public exploits
0
none known

Summary

Irssi 1.2.x before 1.2.2 has a use-after-free if the IRC server sends a double CAP.

Patch / fix

  • irssi irssi 1.2.2
  • irssi Debian 14, Debian 13, Debian 12 1.2.2-1

debian advisories DEBIAN-CVE-2019-15717

  • irssi openSUSE Tumbleweed 1.2.3-2.4

opensuse advisories openSUSE-SU-2024:10865-1

  • irssi Alpine 3.24, Alpine 3.23, Alpine 3.22 +12 more 1.2.2-r0

alpine advisories ALPINE-CVE-2019-15717

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • irssi Arch Linux 1.2.2-1

arch linux advisories AVG-1028

Is CVE-2019-15717 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 Fencer

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-2019-15717 updated cvss 7.5

Irssi: use-after-free if the IRC server sends double CAP

  • Red Hat Enterprise Linux 6 irssi Red Hat Enterprise Linux 7 irssi Red Hat Enterprise Linux 8 irssi
    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

Exploit prediction

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

CVSS scores

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

Classification

Weakness

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.