CVE-2016-4980: Low severity ethz xquest vulnerability

Published Jun 13, 2016
·
Updated

A password generation weakness exists in xquest through 2016-06-13.

Other sources

Kurt Seifried of Red Hat reports:

The xguest rpm creates a user and sets a password using the following rpm postinstall script:

head -1 /dev/urandom | passwd xguest --stdin > /dev/null

this can lead to insufficient randomness being used (in testing with head -n 1 /dev/urandom | wc -c it took an average of 10 attempts to get only 2 characters out). This password is required due to GDM requiring a password for automated passwordless logins at the console.

A better method would be to use a tool such as openssl to get a guaranteed amount of entropy to create the password.

Additionally this password needs to be unique per instance or install but this value is created at install-time and not during the first run. All container and image instances created would share the same password as this password is set at rpm install time, and each instance should recieve a unique password.

This bug is being file because Product Security considers "first run problems" to be bugs with the source package and with the container or image only in the aggregate. This view is in collaboration with upstream Fedora. See: https://fedorahosted.org/fpc/ticket/506

The recommended resolution for services is to follow the "First-time Service Setup" pattern (see: https://fedoraproject.org/wiki/Packaging:InitialServiceSetup ). Other packages may should use a runtime check and generation or similar procedure.

Red Hat

Affected Software

4 affected components
Ethz Xquest<=2016-06-13
Fedoraproject Fedora=23
redhat Enterprise Linux=6.0
redhat Enterprise Linux=7.0

Event History

Jun 13, 2016
Data Sourced
via Red Hat·04:44 PM
DescriptionSeverityAffected Software
Nov 27, 2019
CVE Published
via MITRE·03:55 PM
Data Sourced
via MITRE·03:55 PM
DescriptionWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2016-4980?

CVE-2016-4980 has been rated as having a moderate severity due to its potential to expose user passwords.

2

How do I fix CVE-2016-4980?

To fix CVE-2016-4980, upgrade to a version of xquest released after June 13, 2016 that addresses the password generation weakness.

3

What systems are affected by CVE-2016-4980?

CVE-2016-4980 affects xquest versions through 2016-06-13, Fedora 23, and Red Hat Enterprise Linux versions 6.0 and 7.0.

4

What is the root cause of CVE-2016-4980?

The root cause of CVE-2016-4980 is inadequate randomness in the password generation process implemented in the xguest RPM post-install script.

5

Can CVE-2016-4980 lead to password-related attacks?

Yes, CVE-2016-4980 can potentially lead to password-related attacks due to predictable passwords being generated.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203