What is the severity of CVE-2013-4291?

CVE-2013-4291 is considered a high-severity vulnerability due to its potential to allow local users to gain elevated privileges.

How do I fix CVE-2013-4291?

To mitigate CVE-2013-4291, upgrade to libvirt versions 1.1.2 or later that address this vulnerability.

What versions of libvirt are affected by CVE-2013-4291?

CVE-2013-4291 affects libvirt versions 0.10.2.7, 1.0.5.5, and 1.1.1.

What is the root cause of CVE-2013-4291?

The root cause of CVE-2013-4291 is improper handling of group memberships in the virSecurityManagerSetProcessLabel function.

Can CVE-2013-4291 be exploited remotely?

CVE-2013-4291 cannot be exploited remotely as it requires local access to the system.

Vulnerability/
CVE-2013-4291

medium

6.9

CWE

264

10/9/2013

30/9/2013

6/8/2024

CVE-2013-4291

First published: Tue Sep 10 2013(Updated: )

The virSecurityManagerSetProcessLabel function in libvirt 0.10.2.7, 1.0.5.5, and 1.1.1, when the domain has read an uid:gid label, does not properly set group memberships, which allows local users to gain privileges.

Credit: secalert@redhat.com

Affected Software	Affected Version	How to fix
Red Hat Libvirt	=0.10.2.7
Red Hat Libvirt	=1.0.5.5
Red Hat Libvirt	=1.1.1

Remedy

http://wiki.libvirt.org/page/Maintenance_Releases

Remedy

https://bugzilla.redhat.com/show_bug.cgi?id=1006509

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2013-4291?
CVE-2013-4291 is considered a high-severity vulnerability due to its potential to allow local users to gain elevated privileges.
How do I fix CVE-2013-4291?
To mitigate CVE-2013-4291, upgrade to libvirt versions 1.1.2 or later that address this vulnerability.
What versions of libvirt are affected by CVE-2013-4291?
CVE-2013-4291 affects libvirt versions 0.10.2.7, 1.0.5.5, and 1.1.1.
What is the root cause of CVE-2013-4291?
The root cause of CVE-2013-4291 is improper handling of group memberships in the virSecurityManagerSetProcessLabel function.
Can CVE-2013-4291 be exploited remotely?
CVE-2013-4291 cannot be exploited remotely as it requires local access to the system.

agent/type
agent/first-publish-date
agent/remedy
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/severity
agent/references
agent/author
agent/weakness
agent/description
agent/event
collector/redhat-bugzilla
source/Red Hat
alias/CVE-2013-4291
agent/trending
agent/source
agent/softwarecombine
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/redhat
canonical/red hat libvirt
version/red hat libvirt/0.10.2.7
version/red hat libvirt/1.0.5.5
version/red hat libvirt/1.1.1

Company

Resources

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.

Frequently Asked Questions

What is the severity of CVE-2013-4291?
CVE-2013-4291 is considered a high-severity vulnerability due to its potential to allow local users to gain elevated privileges.
How do I fix CVE-2013-4291?
To mitigate CVE-2013-4291, upgrade to libvirt versions 1.1.2 or later that address this vulnerability.
What versions of libvirt are affected by CVE-2013-4291?
CVE-2013-4291 affects libvirt versions 0.10.2.7, 1.0.5.5, and 1.1.1.
What is the root cause of CVE-2013-4291?
The root cause of CVE-2013-4291 is improper handling of group memberships in the virSecurityManagerSetProcessLabel function.
Can CVE-2013-4291 be exploited remotely?
CVE-2013-4291 cannot be exploited remotely as it requires local access to the system.