Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Network Security

// // //
6/26/2019
07:35 AM
Larry Loeb
Larry Loeb
Larry Loeb

Developers Find Temporary Fix for OpenSSH Remote Access Software Vulnerability

The latest update from the OpenSSH developers encrypts private keys before storing them into the system memory, which will protect the keys against almost all types of side-channel attacks.

Researchers keep coming up with memory side-channel vulnerabilities in modern processors and DRAMs, like Rowhammer, RAMBleed, Spectre and Meltdown. All of these attacks bypass architectural safeguards that are supposed to keep data behind an unscalable wall. The attacks act to infer memory-resident data that is being stored in plaintext for operational reasons.

Now, many researchers have demonstrated their side-channel attacks against the OpenSSH application installed on a targeted computer. This is because OpenSSH keeps a copy of your SSH key available in memory for multiple connections to the same remote server in a session.

OpenSSH is used to remotely access and manage computer systems and servers, and also for other automated machine-to-machine communications. While first designed for OpenBSD, it's also used by default in most Linux distributions today as well as being supported in Windows 10.

The latest update from the OpenSSH developers introduces a new security feature designed to mitigate this problem. It encrypts private keys before storing them into the system memory, which will protect the keys against almost all types of side-channel attacks.

Damien Miller said in the release notes for the update that, "This change encrypts private keys when they are not in use with a symmetric key that is derived from a relatively large 'prekey' consisting of random data (currently 16KB). Attackers must recover the entire prekey with high accuracy before they can attempt to decrypt the shielded private key, but the current generation of attacks have bit error rates that, when applied cumulatively to the entire prekey, make this unlikely. Implementation-wise, keys are encrypted 'shielded' when loaded and then automatically and transparently unshielded when used for signatures or when being saved/serialized."

The team is not looking to make this approach permanent. Indeed, they said that, "Hopefully we can remove this in a few years' time when computer architecture has become less unsafe."

There are limitations to what the developers have come up with. As they state in their patch notes, the technique makes successful side-channel attacks less likely, but not impossible.

The hardware that makes speculative and side-channel attacks possible in the first place will have to change in the future. But, even after that change, there will be legacy computers out there that will remain vulnerable to these kinds of attacks. Anything that can be done to deal with these compromised hardware designs now will have long-lasting effects on the security landscape.

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Machine Learning, AI & Deep Learning Improve Cybersecurity
Machine intelligence is influencing all aspects of cybersecurity. Organizations are implementing AI-based security to analyze event data using ML models that identify attack patterns and increase automation. Before security teams can take advantage of AI and ML tools, they need to know what is possible. This report covers: -How to assess the vendor's AI/ML claims -Defining success criteria for AI/ML implementations -Challenges when implementing AI
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-40826
PUBLISHED: 2022-10-07
B.C. Institute of Technology CodeIgniter <=3.1.13 is vulnerable to SQL Injection via system\database\DB_query_builder.php or_having() function.
CVE-2022-40827
PUBLISHED: 2022-10-07
B.C. Institute of Technology CodeIgniter <=3.1.13 is vulnerable to SQL Injection via system\database\DB_query_builder.php where() function.
CVE-2022-40828
PUBLISHED: 2022-10-07
B.C. Institute of Technology CodeIgniter <=3.1.13 is vulnerable to SQL Injection via system\database\DB_query_builder.php or_where_not_in() function.
CVE-2022-40829
PUBLISHED: 2022-10-07
B.C. Institute of Technology CodeIgniter <=3.1.13 is vulnerable to SQL Injection via system\database\DB_query_builder.php or_like() function.
CVE-2022-40830
PUBLISHED: 2022-10-07
B.C. Institute of Technology CodeIgniter <=3.1.13 is vulnerable to SQL Injection via system\database\DB_query_builder.php where_not_in() function.