Welcome
About
News
Anonymous Reporting
Tools
MCA Chatter
Library
V-ID Terminal
Support
My Account

News

Icon representing US Coast Guard Bulletin: Cyber Adversaries Targeting Commercial Vessels
US Coast Guard Bulletin: Cyber Adversaries Targeting Commercial Vessels

June 21st 2019
Icon representing Would you pay $1m for a laptop full of malware?
Would you pay $1m for a laptop full of malware?

May 23rd 2019
Icon representing Singapore Opens Maritime Cybersecurity Operations Centre (MSOC)
Singapore Opens Maritime Cybersecurity Operations Centre (MSOC)

May 22nd 2019
 
 
 

Leftover Synaptics debugger puts a keylogger on laptops

 
December 11th 2017
HP first to patch, expect others to follow suit
For the second time this year, HP has had to patch its laptops after a security researcher found a driver-level keylogger – and this time, other laptop makers might have to check their own products.

The debug trace was in the Synaptics Touchpad driver used almost across-the-board in HP laptops, and while off by default, a registry entry could turn it on. While few home users would be likely to turn it on, it would be a tasty exploit for RAT (remote access trojan) herders.

The bug was disclosed by “ZwClose”, who was looking through the driver to see if he could adjust the backlighting of HP laptop keyboards.

HP acknowledged the issue, and issued updates for more than 173 commercial products and over 293 consumer products.

ZwClose wrote that a fix will also land in Windows Update.

Consumer items are still awaiting a fix include eight HP Envy variants, an HP Stream series, and an HP x360 11 convertible.

HP's advisory stated that the vulnerability “impacts all Synaptics OEM partners”, so we can expect a rash of driver updates to be released in the fugure. HP added: “Neither Synaptics nor HP has access to customer data as a result of this issue.”

Back in May 2017, security researchers from Swiss outfit Modzero found a keylogger in HP laptops' Conexant audio drivers. As with the latest discovery, the logging was in debugging code the developers forgot to remove from production models.

Source


Keywords