Cloudanix VulnDB

CVE-2015-9543

Low · 3.3

CVSS

3.3

EPSS

0.4%

Published

Feb 19, 2020

CISA due date

—

Cloudanix analysis

Schedule a fix SSVC: Track

A problem in a cloud management system can let anyone who reads its log files take control of virtual machine screens.

Exploitation
Local Privilege
Attacker needs
Low Privilege
Complexity
Low
Impact
Data Exposure
Component
Application
Class
Information Disclosure
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

The flaw writes consoleauth tokens into service log files via NovaProxyRequestHandlerBase.new_websocket_client, allowing any party with log read access to obtain tokens that grant console access to virtual machines in novncproxy setups.

Why it matters to the business

Compromised log access can lead to unauthorized takeover of virtual machine consoles, exposing sensitive workloads and data in affected cloud deployments; the issue has been public for over six years with stable but low exploit likelihood.

How an attack unfolds

An attacker first obtains read access to Nova service logs, locates the leaked consoleauth tokens written during websocket client initialization, then replays those tokens against the novncproxy endpoint to attach to and interact with target virtual machine consoles.

How to fix it

Upgrade OpenStack Nova to 18.2.4, 19.1.0, 20.1.0 or later; for the usvn/usvn package apply commit 08401edbd528c8e3b07bca9a4b320ca1c9d91424. Restrict file-system permissions on all log directories and rotate any tokens that may have been exposed.

How to confirm the fix worked

After upgrade, inspect recent log samples for absence of token strings, confirm the patched websocketproxy.py is deployed, and attempt console connections only with freshly issued tokens.

Typical attack path

  1. Obtain read access to Nova service log files
  2. Parse logs for consoleauth token strings emitted by websocketproxy.py
  3. Submit captured tokens to novncproxy to establish unauthorized console sessions

How to detect it

Review Nova log files and novncproxy access logs for unexpected token values or console attachment events that do not correlate with legitimate user sessions; correlate with authentication events around the time of log entries.

What your security team should do

  • Apply the listed fixed versions or commit without delay
  • Harden log file ACLs so only authorized processes and analysts can read them
  • Audit console access logs for tokens or sessions originating outside expected sources

The record

An issue was discovered in OpenStack Nova before 18.2.4, 19.x before 19.1.0, and 20.x before 20.1.0. It can leak consoleauth tokens into log files. An attacker with read access to the service's logs may obtain tokens used for console access. All Nova setups using novncproxy are affected. This is related to NovaProxyRequestHandlerBase.new_websocket_client in console/websocketproxy.py.

Affected packages

Ecosystem Package Introduced Fixed
PyPI nova 0 18.2.4
PyPI nova 19.0.0 19.1.0
PyPI nova 20.0.0 20.1.0
Debian:11 nova 0 2:20.1.1-1
Debian:12 nova 0 2:20.1.1-1
Debian:13 nova 0 2:20.1.1-1
Ubuntu:18.04:LTS nova 0 2:17.0.13-0ubuntu5.3
Ubuntu:20.04:LTS nova 0 2:21.0.0~b1~git2019120415.45fb747c98-0ubuntu1
Ubuntu:20.04:LTS nova 0 2:21.2.4-0ubuntu2.2
Ubuntu:Pro:16.04:LTS nova 0 2:13.1.4-0ubuntu4.5+esm1
pypi nova 19.0.0 No fix
pypi nova 20.0.0 No fix

Related vulnerabilities