Bug 41719 - libvirt: Authentication issue (4.1)
libvirt: Authentication issue (4.1)
Status: CLOSED WONTFIX
Product: UCS
Classification: Unclassified
Component: Security updates
UCS 4.1
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
:
Depends on: 40317 45635
Blocks:
  Show dependency treegraph
 
Reported: 2016-07-01 18:47 CEST by Janek Walkenhorst
Modified: 2019-04-11 19:24 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Security Issue
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score: 5.6 (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Janek Walkenhorst univentionstaff 2016-07-01 18:47:49 CEST
It was discovered that there was a password policy issue in libvirt, a
library for interfacing with different virtualization systems.

Setting an empty graphics password is documented as a way to disable
VNC/SPICE access, but QEMU does not always behave like that. VNC would
happily accept the empty password. We enforce the behavior by setting
password expiration to "now".

(CVE-2016-5008)

For Debian 7 "Wheezy", this issue has been fixed in libvirt version
0.9.12.3-1+deb7u2.
Comment 1 Arvid Requate univentionstaff 2017-11-01 17:13:12 CET
In UCS 4.1 we shipped 1.2.9-9~bpo70+1 from wheezy-backports, so none of the above applies. Instead we have to monitor the Debian jessie version here and backport patches if applicable. In errata4.1-1 we patched the package to deb8u2.


Upstream Debian package version 1.2.9-9+deb8u3 fixed:

* Let empty default VNC password work as documented (CVE-2016-5008)
Comment 2 Arvid Requate univentionstaff 2018-04-17 15:56:17 CEST
This issue has been filed against UCS 4.1.

UCS 4.1 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.