Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1529176 - (CVE-2017-17840) CVE-2017-17840 iscsi-initiator-utils: Heap-based buffer overflow in process_iscsid_broadcast()
CVE-2017-17840 iscsi-initiator-utils: Heap-based buffer overflow in process_i...
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20171222,repor...
: Security
Depends On: 1529177
Blocks: 1524601
  Show dependency treegraph
 
Reported: 2017-12-26 16:47 EST by Pedro Sampaio
Modified: 2018-01-09 08:54 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-01-09 08:47:44 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Pedro Sampaio 2017-12-26 16:47:38 EST
An issue was discovered in Open-iSCSI through 2.0.875. A local attacker can cause the iscsiuio server to abort or potentially execute code by sending messages with incorrect lengths, which (due to lack of checking) can lead to buffer overflows, and result in aborts (with overflow checking enabled) or code execution. The process_iscsid_broadcast function in iscsiuio/src/unix/iscsid_ipc.c does not validate the payload length before a write operation.

Upstream patch:

https://github.com/open-iscsi/open-iscsi/pull/72
Comment 1 Pedro Sampaio 2017-12-26 16:48:11 EST
Created iscsi-initiator-utils tracking bugs for this issue:

Affects: fedora-all [bug 1529177]
Comment 2 Raphael Sanchez Prudencio 2018-01-09 08:54:11 EST
Statement:

Red Hat Product Security has rated this issue as having Moderate 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.