What is the severity of CVE-2015-0259?

CVE-2015-0259 is classified as a high severity vulnerability due to the potential for authentication hijacking.

How do I fix CVE-2015-0259?

To fix CVE-2015-0259, you should upgrade OpenStack Compute (Nova) to version 2014.1.4 or later, or 2014.2.3 or later.

What systems are affected by CVE-2015-0259?

CVE-2015-0259 affects OpenStack Compute (Nova) before version 2014.1.4, 2014.2.x before 2014.2.3, and certain milestones of 2015.1.0.

What types of attacks can occur due to CVE-2015-0259?

CVE-2015-0259 allows remote attackers to hijack user authentication, potentially gaining unauthorized access to console sessions.

Is CVE-2015-0259 still relevant today?

While CVE-2015-0259 is from 2015, it remains relevant for users of outdated OpenStack versions that have not been patched.

Vulnerability/
CVE-2015-0259

medium

5.1

CWE

345

1/4/2015

6/8/2024

CVE-2015-0259

First published: Wed Apr 01 2015(Updated: )

OpenStack Compute (Nova) before 2014.1.4, 2014.2.x before 2014.2.3, and kilo before kilo-3 does not validate the origin of websocket requests, which allows remote attackers to hijack the authentication of users for access to consoles via a crafted webpage.

Credit: secalert@redhat.com

Affected Software	Affected Version	How to fix
OpenStack Nova	>=2014.1<2014.1.4
OpenStack Nova	>=2014.2<2014.2.3
OpenStack Nova	=2015.1.0-milestone1
OpenStack Nova	=2015.1.0-milestone2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2015-0259?
CVE-2015-0259 is classified as a high severity vulnerability due to the potential for authentication hijacking.
How do I fix CVE-2015-0259?
To fix CVE-2015-0259, you should upgrade OpenStack Compute (Nova) to version 2014.1.4 or later, or 2014.2.3 or later.
What systems are affected by CVE-2015-0259?
CVE-2015-0259 affects OpenStack Compute (Nova) before version 2014.1.4, 2014.2.x before 2014.2.3, and certain milestones of 2015.1.0.
What types of attacks can occur due to CVE-2015-0259?
CVE-2015-0259 allows remote attackers to hijack user authentication, potentially gaining unauthorized access to console sessions.
Is CVE-2015-0259 still relevant today?
While CVE-2015-0259 is from 2015, it remains relevant for users of outdated OpenStack versions that have not been patched.

collector/nvd-index
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/weakness
agent/author
agent/references
agent/description
agent/tags
agent/event
agent/first-publish-date
agent/source
vendor/openstack
canonical/openstack nova
version/openstack nova/2014.1
version/openstack nova/2014.2
version/openstack nova/2015.1.0-milestone1
version/openstack nova/2015.1.0-milestone2

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-0259?
CVE-2015-0259 is classified as a high severity vulnerability due to the potential for authentication hijacking.
How do I fix CVE-2015-0259?
To fix CVE-2015-0259, you should upgrade OpenStack Compute (Nova) to version 2014.1.4 or later, or 2014.2.3 or later.
What systems are affected by CVE-2015-0259?
CVE-2015-0259 affects OpenStack Compute (Nova) before version 2014.1.4, 2014.2.x before 2014.2.3, and certain milestones of 2015.1.0.
What types of attacks can occur due to CVE-2015-0259?
CVE-2015-0259 allows remote attackers to hijack user authentication, potentially gaining unauthorized access to console sessions.
Is CVE-2015-0259 still relevant today?
While CVE-2015-0259 is from 2015, it remains relevant for users of outdated OpenStack versions that have not been patched.