Facebook Google Plus Twitter LinkedIn YouTube RSS Menu Search Resource - BlogResource - WebinarResource - ReportResource - Eventicons_066 icons_067icons_068icons_069icons_070

[R1] NetMotion Mobility VPN nmdrv.sys TCP Connection Termination Handling Remote DoS

High

Synopsis

While working on a customer issue, Tenable discovered an issue in the NetMotion Mobility VPN client that lead to a remote crash of Windows 7 Enterprise SP1 (x86 architecture). Tenable performed analysis enough to assist NetMotion in fixing the issue, but did not have the time to do a full investigation. This issue may represent an underlying issue in Windows, but this was only investigated as far as determining that nmdrv.sys is not supposed to call tdtcp!_TdDisconnectHandler() when a server closes a connection, which could result in a "use-after-free" leading to a system crash.

Due to extensive delays in obtaining CVE assignments, Tenable is assigning our own CVE ID that we feel will not conflict with any current assignments or CNA pools. This will assist researchers and vendors in referencing this vulnerability should they work with the named vendor, or other vendors impacted by the issue. Until CVE resolves the delays in assignment, which is currently being discussed by MITRE and the CVE Editorial Board, Tenable will self-assign CVE IDs in the range of CVE-YEAR-82000 through CVE-YEAR-82999. These can be added to the master CVE database trivially, as seen by CVE-2014-999999 This is being done primarily so that we continue to be CVE-Compatible.

Solution

NetMotion has released version 10.50 which fixes this issue.

Disclosure Timeline

2014-01-06 - Tenable informs NetMotion
2014-01-06 - NetMotion acknowledges mail
2014-01-10 - NetMotion releases 10.50 to fix, Release Notes do not mention

All information within TRA advisories is provided “as is”, without warranty of any kind, including the implied warranties of merchantability and fitness for a particular purpose, and with no guarantee of completeness, accuracy, or timeliness. Individuals and organizations are responsible for assessing the impact of any actual or potential security vulnerability.

Tenable takes product security very seriously. If you believe you have found a vulnerability in one of our products, we ask that you please work with us to quickly resolve it in order to protect customers. Tenable believes in responding quickly to such reports, maintaining communication with researchers, and providing a solution in short order.

For more details on submitting vulnerability information, please see our Vulnerability Reporting Guidelines page.

If you have questions or corrections about this advisory, please email [email protected]