RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1387961 - CVE-2016-5180 c-ares: Single byte out of buffer write [RHEL-6]
Summary: CVE-2016-5180 c-ares: Single byte out of buffer write [RHEL-6]
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: c-ares
Version: 6.9
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jakub Hrozek
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: CVE-2016-5180
TreeView+ depends on / blocked
 
Reported: 2016-10-24 04:37 UTC by Japheth Cleaver
Modified: 2017-11-14 21:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1380466
Environment:
Last Closed: 2017-11-14 21:16:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Japheth Cleaver 2016-10-24 04:37:12 UTC 
Please see Bug #1380464 - et seq, through Bug #1380468

c-ares was added to RHEL6 as documented in Bug #513673. The security fix referenced here (and version bump) was applied to EPEL5, EPEL7, and all Fedora versions, but not the standard c-ares package in RHEL6, as far as I can tell.




+++ This bug was initially created as a clone of Bug #1380466 +++

This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora EPEL.

For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.

For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs

When submitting as an update, use the fedpkg template provided in the next
comment(s).  This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.

Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.

[bug automatically created by: add-tracking-bugs]

--- Additional comment from Adam Mariš on 2016-09-29 12:32:16 EDT ---


Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug.  This will ensure that all associated bugs get updated
when new packages are pushed to stable.

=====

# bugfix, security, enhancement, newpackage (required)
type=security

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=1380463,1380466

# Description of your update
notes=Security fix for CVE-2016-5180

# Enable request automation based on the stable/unstable karma thresholds
autokarma=True
stable_karma=3
unstable_karma=-3

# Automatically close bugs when this marked as stable
close_bugs=True

# Suggest that users restart after update
suggest_reboot=False

======

Additionally, you may opt to use the bodhi web interface to submit updates:

https://bodhi.fedoraproject.org/updates/new

--- Additional comment from Fedora Update System on 2016-10-01 00:45:53 EDT ---

c-ares-1.12.0-1.el5 has been pushed to the Fedora EPEL 5 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-c9c041384d

--- Additional comment from Fedora Update System on 2016-10-20 06:18:00 EDT ---

c-ares-1.12.0-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
Comment 2 Adam Mariš 2016-10-24 11:32:43 UTC 
Product Security rated this as having Moderate security impact and currently does not plan to address this issue in RHEL products. Note that impact of this issue on RHEL is less severe than impact on ChromeOS.
Comment 3 Japheth Cleaver 2016-10-25 01:48:00 UTC 
(In reply to Adam Mariš from comment #2)
> Product Security rated this as having Moderate security impact and currently
> does not plan to address this issue in RHEL products. Note that impact of
> this issue on RHEL is less severe than impact on ChromeOS.

While noted, this does lead to the strange result that it's fixed for EL5 and EL7 users, but not those on EL6.

Furthermore, mingw-c-ares was updated in EL6, but the main c-ares package wasn't. This could easily lead to confusion.


I understand the specific chain of reasoning for the EL6 package... But this is one of those cases where I'd ask that the team reconsider this, and either backport the patch or also perform the rebase here too.
Comment 4 Jakub Hrozek 2017-11-14 21:16:43 UTC 
I'm sorry, but given that RHEL-6 in in Production Phase 3 and given the reasoning in comment #2, I'm closing this bug as WONTFIX.

I understand the reasoning in comment #3, but I'm afraid we cannot fix bugs with this severity at this point of RHEL-6 lifecycle.
Note You need to log in before you can comment on or make changes to this bug.