Bug 1459457 (CVE-2017-9469) - CVE-2017-9469 irssi: Invalid read when receiving certain incorrectly quoted DCC files
Summary: CVE-2017-9469 irssi: Invalid read when receiving certain incorrectly quoted D...
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2017-9469
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1459458
Blocks: 1459459
TreeView+ depends on / blocked
 
Reported: 2017-06-07 08:24 UTC by Andrej Nemec
Modified: 2021-02-17 02:02 UTC (History)
4 users (show)

Fixed In Version: irssi 1.0.3
Doc Type: If docs needed, set a value
Doc Text:
An out-of-bound heap read was found in irssi's get_file_params_count() function, during the parsing of a DCC SEND request. An IRC client connected to the same IRC network as the target could send a specially crafted request that would force irssi to read 1 byte outside of an allocated string, which could, possibly, lead to an invalid memory read.
Clone Of:
Environment:
Last Closed: 2017-06-12 14:54:04 UTC

Attachments (Terms of Use)

Description Andrej Nemec 2017-06-07 08:24:12 UTC 
When receiving certain incorrectly quoted DCC files, Irssi would try to find the terminating quote one byte before the allocated memory. A remote attacker could possibly use this to crash irssi.

External References:

https://irssi.org/security/irssi_sa_2017_06.txt
Comment 1 Andrej Nemec 2017-06-07 08:25:03 UTC 
Created irssi tracking bugs for this issue:

Affects: fedora-all [bug 1459458]
Comment 2 Cedric Buissart 2017-06-12 13:58:20 UTC 
Lowering impact: the vulnerability allows an out of bound read 1 byte outside of the allocated memory. As shipped in RHEL, this will not cause an invalid memory access.
Comment 3 Cedric Buissart 2017-06-12 14:54:12 UTC 
Statement:

Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.
Note You need to log in before you can comment on or make changes to this bug.