lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date: Wed, 2 Jan 2019 22:49:42 +1100
From: Filip Palian <>
Subject: [FD] BMC Network Automation v8.7 - remote session hijacking.

Hejkum kejkum,

The BMC Network Automation allows authenticated users to hijack
established remote sessions of other users, version v8.7.00.000 b383
u038 was confirmed to be vulnerable.

Authenticated users of the BMC Network Automation web application with
assigned “viewer” role are able to hijack SSH/Telnet sessions
initiated by other, privileged users.
In order to hijack an established session, the only requirement is to
obtain a valid "terminalJobKey" of that session.
A valid "terminalJobKey" can be obtained through enumeration of the
possible values.
This process is aided by the fact that the format of the
"terminalJobKey" is known and newly generated values are sequential
thus predictable.
The format of a "terminalJobKey" was found to be DDDDDDDDD-DDDDDD,
where "D" is a digit from 0-9 range.
The vulnerable application was found to increment the value of
"terminalJobKey" parameter by one (1) at the last position for each
newly initiated remote session.

Proof of Concept:
1. Privileged user initiates an SSH connection and a new terminal
window is opened with the following sample URL, e.g.:

2. In the next step a non-privileged user enumerates "terminalJobKey"
values until he finds a valid one and is able to hijack the already
established session:

Contact vendor directly for remediation guidance.

07.11.2018: Email detailing discovered issue sent to BMC at
08.11.2018: BMC confirms receipt of the report.
21.11.2018: Follow-up email sent to BMC asking for status.
10.12.2018: Follow-up email sent to BMC informing that the security
advisory will be published in the next following weeks.
02.01.2019: The advisory has been released.

Filip Palian

Sent through the Full Disclosure mailing list
Web Archives & RSS:

Powered by blists - more mailing lists