Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1059520 - (CVE-2014-0042) CVE-2014-0042 OpenStack openstack-heat-templates: setting gpgcheck=0 for signed packages
CVE-2014-0042 OpenStack openstack-heat-templates: setting gpgcheck=0 for sign...
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20140109,reported=2...
: Security
Depends On: 1059525 1059526
Blocks: 1059524
  Show dependency treegraph
 
Reported: 2014-01-29 23:37 EST by Kurt Seifried
Modified: 2016-04-26 16:48 EDT (History)
17 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-05-29 19:31:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2014:0579 normal SHIPPED_LIVE Low: openstack-heat-templates security update 2014-05-29 20:26:58 EDT

  None (edit)
Description Kurt Seifried 2014-01-29 23:37:24 EST
Grant Murphy of the Red Hat Product Security team reports:

there are a number of yum repositories that are configured with gpgcheck=0 but
have rpms that are signed (e.g. Jenkins).

External reference:
https://bugs.launchpad.net/heat-templates/+bug/1267635
https://github.com/openstack/heat-templates/
Comment 3 Kurt Seifried 2014-02-24 13:54:09 EST
Acknowledgements:

This issue was discovered by Grant Murphy of the Red Hat Product Security Team.
Comment 5 errata-xmlrpc 2014-05-29 16:34:39 EDT
This issue has been addressed in following products:

  OpenStack 4 for RHEL 6

Via RHSA-2014:0579 https://rhn.redhat.com/errata/RHSA-2014-0579.html

Note You need to log in before you can comment on or make changes to this bug.