What is the severity of CVE-2015-4037?

CVE-2015-4037 has a severity rating that indicates it can lead to denial of service (DoS) for Qemu guests.

How do I fix CVE-2015-4037?

To fix CVE-2015-4037, you should update to QEMU version 2.3.1 or later, where this vulnerability is addressed.

Which versions of QEMU are affected by CVE-2015-4037?

CVE-2015-4037 affects QEMU versions up to and including 2.3.0.

What capabilities does the CVE-2015-4037 vulnerability impact?

CVE-2015-4037 specifically impacts the user mode networking stack of QEMU when using the -smb option.

Can an unprivileged user exploit CVE-2015-4037?

Yes, an unprivileged user can exploit CVE-2015-4037 to disrupt the instantiation of Qemu guests.

Vulnerability/
CVE-2015-4037

low

1.9

CWE

19/5/2015

26/8/2015

6/8/2024

CVE-2015-4037

First published: Tue May 19 2015(Updated: )

Qemu's user mode networking stack(SLiRP) is vulnerable to a predictable temporary file names creation flaw. It occurs when using -smb option. An unprivileged user could use this to thwart instantiation of Qemu guests, resulting in DoS. Reference: -> <a href="http://seclists.org/oss-sec/2015/q2/426">http://seclists.org/oss-sec/2015/q2/426</a>

Credit: secalert@redhat.com

Affected Software	Affected Version	How to fix
QEMU KVM	<=2.3.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2015-4037?
CVE-2015-4037 has a severity rating that indicates it can lead to denial of service (DoS) for Qemu guests.
How do I fix CVE-2015-4037?
To fix CVE-2015-4037, you should update to QEMU version 2.3.1 or later, where this vulnerability is addressed.
Which versions of QEMU are affected by CVE-2015-4037?
CVE-2015-4037 affects QEMU versions up to and including 2.3.0.
What capabilities does the CVE-2015-4037 vulnerability impact?
CVE-2015-4037 specifically impacts the user mode networking stack of QEMU when using the -smb option.
Can an unprivileged user exploit CVE-2015-4037?
Yes, an unprivileged user can exploit CVE-2015-4037 to disrupt the instantiation of Qemu guests.

agent/type
agent/softwarecombine
agent/first-publish-date
collector/mitre-cve
source/MITRE
collector/redhat-bugzilla
source/Red Hat
alias/CVE-2015-4037
agent/last-modified-date
agent/severity
agent/author
agent/references
agent/weakness
agent/description
agent/event
agent/trending
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/qemu
canonical/qemu kvm
version/qemu kvm/2.3.0

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-2015-4037?
CVE-2015-4037 has a severity rating that indicates it can lead to denial of service (DoS) for Qemu guests.
How do I fix CVE-2015-4037?
To fix CVE-2015-4037, you should update to QEMU version 2.3.1 or later, where this vulnerability is addressed.
Which versions of QEMU are affected by CVE-2015-4037?
CVE-2015-4037 affects QEMU versions up to and including 2.3.0.
What capabilities does the CVE-2015-4037 vulnerability impact?
CVE-2015-4037 specifically impacts the user mode networking stack of QEMU when using the -smb option.
Can an unprivileged user exploit CVE-2015-4037?
Yes, an unprivileged user can exploit CVE-2015-4037 to disrupt the instantiation of Qemu guests.