Threatpost reported that a Transmission Control Protocol (TCP) flaw has resided in the Linux implementation since 2012, or since v3.6 of the kernel. The flaw affects all internet users and puts them at risk — not just the ones directly on Linux systems.

At least that’s what security experts are saying. Researchers from the University of California, Riverside and the U.S. Army Research Laboratory delivered a paper at the USENIX Security Symposium, “Off-Path TCP Exploits: Global Rate Limit Considered Dangerous,” that outlined the problem and suggested some mitigation strategies.

A Subtle TCP Flaw

UCR said in a press statement that it had discovered a subtle flaw in the Linux software in the form of side channels. Attackers can exploit the flaw to infer the TCP sequence numbers associated with a particular connection. The only information cybercriminals need to carry out this type of attack is the IP address of the communicating parties.

Encrypted connections, the researchers said, are immune to data injection. However, those encrypted connections can still be forcefully terminated by the attacker. According to UCR, the attack can be executed in less than a minute and has a 90 percent success rate.

No user action is necessary to carry out this attack. In fact, users could become victims without doing anything wrong from a security standpoint, such as inadvertently downloading malware or clicking on a link in a phishing email.

The researchers created a short video showing how the attacks works.

A Simple Remedy

The researchers alerted Linux about the vulnerability. There are now patches that can be applied to the latest Linux version.

Until those Linux patches are applied across the board, however, one UCR researcher recommended a temporary patch that can be applied to both client and server hosts. The patch simply raises the challenge ACK limit to a very large value, which makes it “practically impossible” to exploit the side channel, the press statement noted.

Performing the change to that parameter can be as simple as adding one line to the sysctl.conf file and then updating. It’s rare that such a major vulnerability can be so simply remedied — and as such leaves no room for excuses when it comes to patching.

More from

Why Cybersecurity Risk Assessment Matters in the Banking Industry

When customers put money in a bank, they need to trust it will stay there. Because of the high stakes involved for the customer, such as financial loss, and how long it takes to resolve fraud and potential identity theft, customers are sensitive to the security of the bank as well as fraud prevention measures. Banks that experience high volumes of fraud are likely to lose customers and revenue. The key is to protect customers and their accounts before problems…

What CISOs Should Know About CIRCIA Incident Reporting

In March of 2022, a new federal law was adopted: the Cyber Incident Reporting Critical Infrastructure Act (CIRCIA). This new legislation focuses on reporting requirements related to cybersecurity incidents and ransomware payments. The key takeaway: covered entities in critical infrastructure will now be required to report incidents and payments within specified time frames to the Cybersecurity and Infrastructure Security Agency (CISA). These new requirements will change how CISOs handle cyber incidents for the foreseeable future. As a result, CISOs must…

Will the 2.5M Records Breach Impact Student Loan Relief?

Over 2.5 million student loan accounts were breached in the summer of 2022, according to a recent Maine Attorney General data breach notification. The target of the breach was Nelnet Servicing, a servicing system and web portal provider for the Oklahoma Student Loan Authority (OSLA) and EdFinancial. An investigation determined that intruders accessed student loan account registration information between June and July 2022. The stolen data includes names, addresses, emails, phone numbers and social security numbers for 2,501,324 student loan…

Containers, Security, and Risks within Containerized Environments

Applications have historically been deployed and created in a manner reminiscent of classic shopping malls. First, a developer builds the mall, then creates the various stores inside. The stores conform to the dimensions of the mall and operate within its floor plan. In older approaches to application development, a developer would have a targeted system or set of systems for which they intend to create an application. This targeted system would be the mall. Then, when building the application, they would…