Bug 1459456 (CVE-2017-9468)

Summary: CVE-2017-9468 irssi: Null pointer dereference while receiving a DCC message without source nick/host
Product: [Other] Security Response Reporter: Andrej Nemec <anemec>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED WONTFIX QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: huzaifas, jskarvad, mmahut, rosser.bjr
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: irssi 1.0.3 Doc Type: If docs needed, set a value
Doc Text:
A null pointer dereference was found in the way irssi handles DCC messages that do not contain a source nick/host. A malicious IRC server could be used to crash an irssi client by sending a specially crafted DCC message.
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-12 08:11:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1459458    
Bug Blocks: 1459459    

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/.