Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1459456 (CVE-2017-9468) - CVE-2017-9468 irssi: Null pointer dereference while receiving a DCC message without source nick/host
Summary: CVE-2017-9468 irssi: Null pointer dereference while receiving a DCC message w...
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2017-9468
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:
TreeView+ depends on / blocked
 
Reported: 2017-06-07 08:20 UTC by Andrej Nemec
Modified: 2021-02-17 02:03 UTC (History)
4 users (show)

Fixed In Version: irssi 1.0.3
Clone Of:
Environment:
Last Closed: 2017-06-12 08:11:37 UTC
Embargoed:

Attachments (Terms of Use)

Description Andrej Nemec 2017-06-07 08:20:15 UTC 
When receiving a DCC message without source nick/host, Irssi would attempt to dereference a NULL pointer. A malicious remote server could cause irssi to crash.

External References:

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

Affects: fedora-all [bug 1459458]
Comment 2 Cedric Buissart 2017-06-12 08:04:43 UTC 
Lowering severity because of the following reason :
* A rogue, or buggy, IRC server is required to be able to make use of this vulnerability. An attacker would need to either gain control of a IRC server, or trick the user into connecting a rogue IRC server
Comment 3 Cedric Buissart 2017-06-12 08:11:08 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.