Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1186717

Summary: update for CVE-2015-0235 missed by yum --security
Product: Red Hat Enterprise Linux 6 Reporter: Dave Love <dave.love>
Component: yumAssignee: Valentina Mukhamedzhanova <vmukhame>
Status: CLOSED NOTABUG QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.6CC: ashankar, dave.love, james.antill, lopaka, pfrankli, spoyarek, vmukhame
Target Milestone: rcKeywords: Security
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-13 11:02:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dave Love 2015-01-28 11:49:53 UTC
Description of problem:

Security updates relying on yum --security (e.g. via yum-cron) don't pick up the GHOST fix.

I don't know how yum-security works, so I don't know whether the bug is actually in the repo, glibc package, or elsewhere.

Version-Release number of selected component (if applicable):

2.12-1.149.el6_6.5

How reproducible:


Steps to Reproduce:

# yum --security check-update glibc\*

Actual results:

# yum --security check-update glibc\*
Loaded plugins: auto-update-debuginfo, changelog, downloadonly, etckeeper,
              : fastestmirror, filter-data, merge-conf, post-transaction-
              : actions, priorities, product-id, protectbase, refresh-
              : packagekit, security, subscription-manager, verify, versionlock
Loading mirror speeds from cached hostfile
 * epel: mirror.bytemark.co.uk
 * epel-debuginfo: mirror.bytemark.co.uk
Skipping filters plugin, no data
0 packages excluded due to repository protections
Limiting package lists to security relevant ones
No packages needed for security; 45 packages available

Expected results:

# yum check-update glibc\*
Loaded plugins: auto-update-debuginfo, changelog, downloadonly, etckeeper,
              : fastestmirror, filter-data, merge-conf, post-transaction-
              : actions, priorities, product-id, protectbase, refresh-
              : packagekit, security, subscription-manager, verify, versionlock
Loading mirror speeds from cached hostfile
 * epel: mirror.bytemark.co.uk
 * epel-debuginfo: mirror.bytemark.co.uk
Skipping filters plugin, no data
0 packages excluded due to repository protections

glibc.i686                      2.12-1.149.el6_6.5            rhel-6-server-rpms
glibc.x86_64                    2.12-1.149.el6_6.5            rhel-6-server-rpms
glibc-common.x86_64             2.12-1.149.el6_6.5            rhel-6-server-rpms
glibc-devel.i686                2.12-1.149.el6_6.5            rhel-6-server-rpms
glibc-devel.x86_64              2.12-1.149.el6_6.5            rhel-6-server-rpms
glibc-headers.x86_64            2.12-1.149.el6_6.5            rhel-6-server-rpms

Additional info:

Comment 2 Siddhesh Poyarekar 2015-01-28 14:28:15 UTC
Not a glibc issue.  Moving to yum.

Comment 3 Valentina Mukhamedzhanova 2015-02-04 12:29:29 UTC
I can't reproduce this issue, 'yum --security check-update glibc\*' gives me the expected output.

Are you still facing this problem? It could be helpful to try to disable all plugins except product-id, security and subscription-manager, clear the cache and try again.

Comment 4 Dave Love 2015-02-09 17:33:39 UTC
I can no longer reproduce this, but I have no idea what might have changed.
Could you tell me what metadata yum-plugin-security uses so I can try to figure it
out without having to read the source?  (It gives me false positives with
check-update too, which are still present.)

Comment 5 Valentina Mukhamedzhanova 2015-02-13 11:02:42 UTC
yum-plugin-security uses the updateinfo metadata (something like /var/cache/yum/x86_64/6Server/rhel-6-server-rpms/6189da8c10e23e0a4b0ce14e30131e484ff83070d3a7db43152bf27da436a87e-updateinfo.xml.gz)

Since the issue cannot be reproduced, I am closing this. Please feel free to reopen if you have a reliable reproducer.