Bug 1132002

Summary: lxc: default predictable root password in most templates [fedora-all]
Product: [Fedora] Fedora Reporter: Vincent Danen <vdanen>
Component: lxcAssignee: Thomas Moschny <thomas.moschny>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 23CC: karlthered, pj.pandit, sagarun, thomas.moschny
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: fst_ping=1,fst_owner=pjp
Fixed In Version: Doc Type: Release Note
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 12:50:37 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:02 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.

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.

NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time.  If you need to fix the versions independent of each other,
you may clone this bug as appropriate.

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

Comment 1 Vincent Danen 2014-08-20 13:38:04 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,1132002

# 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,1132002

Comment 2 pjp 2014-12-03 18:30:26 UTC
Hello thomas.moschny,

Could you please fix this soon?

Comment 3 Thomas Moschny 2014-12-03 19:42:47 UTC
(In reply to pjp from comment #2)
> Hello thomas.moschny,
> 
> Could you please fix this soon?

This has to be fixed upstream. There's already discussion, see:
https://lists.linuxcontainers.org/pipermail/lxc-devel/2014-August/010077.html

I've also pinged there:
https://lists.linuxcontainers.org/pipermail/lxc-devel/2014-August/010121.html

I expect this to be fixed in the next major release of LXC.

As noted in bug 1132001, it is unclear whether this really qualifies as a security issue. Someone has to manually and willingly create and run a container, and the password can be configured and/or changed after creation of the container.

Comment 4 pjp 2014-12-05 17:57:50 UTC
  Hello Thomas,

(In reply to Thomas Moschny from comment #3)
> This has to be fixed upstream. There's already discussion, see:
> https://lists.linuxcontainers.org/pipermail/lxc-devel/2014-August/010077.html
> https://lists.linuxcontainers.org/pipermail/lxc-devel/2014-August/010121.html
> 
> I expect this to be fixed in the next major release of LXC.

  I see. Thanks so much for the details. 
 
> As noted in bug 1132001, it is unclear whether this really qualifies as a
> security issue. Someone has to manually and willingly create and run a
> container, and the password can be configured and/or changed after creation
> of the container.

  Right, I think it's more of hardening than a security issue. But still makes sense to have the bug open. It's better to have stronger defaults.

Thank you.

Comment 5 pjp 2015-04-09 17:33:33 UTC
Hello thomas.moschny,

You plan to fix this soon?

Comment 6 Thomas Moschny 2015-04-26 07:46:33 UTC
(In reply to pjp from comment #5)
> Hello thomas.moschny,
> 
> You plan to fix this soon?

As far as I can see, upstream hasn't fixed this for all templates.

Comment 7 Fedora End Of Life 2015-05-29 12:41:11 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 pjp 2015-05-29 18:03:36 UTC
(In reply to Thomas Moschny from comment #6)
> As far as I can see, upstream hasn't fixed this for all templates.

 Ie. it is partially fixed for a subset of templates?

Are LXC versions in F22/rawhide affected by this issue? If so, we need to move this bug to the affected latest version. If not, I think we could close this with
cantfix/wontfix or eol.

Comment 9 Thomas Moschny 2015-06-17 16:20:57 UTC
(In reply to pjp from comment #8)
> Are LXC versions in F22/rawhide affected by this issue?

Yes. The effort to push upstream for a solution has been renewed, see bug 1132004.

Comment 10 Jan Kurik 2015-07-15 14:38:29 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23

Comment 11 Fedora End Of Life 2016-11-24 11:12:31 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 12 Fedora End Of Life 2016-12-20 12:50:37 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.