Bug 1132004

Summary:	lxc: default predictable root password in most templates [epel-7]
Product:	[Fedora] Fedora EPEL	Reporter:	Vincent Danen <vdanen>
Component:	lxc	Assignee:	Thomas Moschny <thomas.moschny>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	epel7	CC:	karlthered, pj.pandit, sagarun, thomas.moschny
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:	fst_owner=mhayden
Fixed In Version:		Doc Type:	Release Note
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-07-08 22:03:22 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1132001

Description Vincent Danen 2014-08-20 13:38:10 UTC

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.

epel-7 tracking bug for lxc: see blocks bug list for full details of the security issue(s).

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

Comment 1 Vincent Danen 2014-08-20 13:38:14 UTC

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=1132001,1132004

# Description of your update
notes=Security fix for 

# 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 update submission link instead:

https://admin.fedoraproject.org/updates/new/?type_=security&bugs=1132001,1132004

Comment 2 Major Hayden 🤠 2015-06-16 12:38:02 UTC

Thread started on the lxc-devel list: https://lists.linuxcontainers.org/pipermail/lxc-devel/2015-June/011883.html

Comment 3 Thomas Moschny 2015-06-16 12:44:59 UTC

Thanks for bringing this up again upstream!

Note that earlier discussions here in Bugzilla took place in bug 1132002.

Comment 4 Major Hayden 🤠 2015-06-16 12:48:02 UTC

Thanks, Thomas.  This looks like it could be a duplicate of bug 1132002.  Should this one be closed in favor of that one?  Eric bumped that ticket to rawhide just last week.

Comment 5 Thomas Moschny 2015-06-16 12:59:19 UTC

I don't think so. I am not totally familiar with the Fedora security bug handling, but the structure seems to be like this:

tracker: bug 1132001
-> fedora (all): bug 1132002
-> epel6: bug 1132003
-> epel7: bug 1132004

We currently have
  LXC 1.0.x in f20, f21, epel6, and epel7
  LXC 1.1.x in f22+

As far as I know, all released LXC versions are more or less affected by this issue.

Comment 6 pjp 2015-06-18 20:18:01 UTC

(In reply to Thomas Moschny from comment #5)
> I don't think so. I am not totally familiar with the Fedora security bug
> handling, but the structure seems to be like this:
> 
> tracker: bug 1132001
> -> fedora (all): bug 1132002
> -> epel6: bug 1132003
> -> epel7: bug 1132004

  That's correct. Each security bug has a top level parent bug and each product Fedora, EPEL etc. have separate tracker bugs.

  -> https://fedoraproject.org/wiki/Security_Team#CVEs

Comment 7 Troy Dawson 2024-07-08 22:03:22 UTC

EPEL 7 entered end-of-life (EOL) status on 2024-06-30.\n\nEPEL 7 is no longer maintained, which means that it\nwill not receive any further security or bug fix updates.\n As a result we are closing this bug.