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.

Comments
Decades-Old Vulnerability Threatens Internet Of Things
Newest First  |  Oldest First  |  Threaded View
Kelly Jackson Higgins
50%
50%
Kelly Jackson Higgins,
User Rank: Strategist
6/30/2014 | 7:47:37 AM
Re: Perhaps not actually reachable in the real world
That's a great question. There wasn't any specific guidance thus far on how to scan for it, but the recommendation was to update any apps that use the affected libraries, all of which now have patches. Don Bailey is planning to provide more details on the vuln beyond his initial post, so maybe we'll see more detection info there.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
6/28/2014 | 10:00:00 PM
Re: Perhaps not actually reachable in the real world
Very true. Has there been any documentation/data on how to scan for this and what tools would be the most efficient to do so?

I am sure vulnerability scanners  would be able to but thus far has there been any that have stepped up to say that they can quickly and passively scan for this? Or has this been dismissed because the quantity of people this could effect has been difficult to calculate?
Kelly Jackson Higgins
50%
50%
Kelly Jackson Higgins,
User Rank: Strategist
6/27/2014 | 7:26:16 AM
Re: Long elapse of time
This isn't the first open-source vuln and it won't be the last, for sure. Patching is always a headache, but even moreso when an open source tool is used in so many places and in so many iterations. Some products won't ever get patched, and many users won't even know their product (based on whatever vulnerable open source tool) is at risk. No easy solutions here. 
Kelly Jackson Higgins
50%
50%
Kelly Jackson Higgins,
User Rank: Strategist
6/27/2014 | 7:14:50 AM
Re: Perhaps not actually reachable in the real world
Indeed, it doesn't mean every single LZO implementation is affected. As Bailey says, each implementation needs to be evaluated for the flaw.
li'l ciso
50%
50%
li'l ciso,
User Rank: Strategist
6/27/2014 | 3:45:03 AM
Perhaps not actually reachable in the real world
The severity of this issue needs to be tempered with the evaluation that most products do not ship with a configuration that allows the issue to be triggered:

Debunking the LZ4 "20 years old bug" myth



 
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
6/26/2014 | 10:02:42 PM
Long elapse of time
Interesting the this vulnerability didn't have similar attributes as other vulnerabilities. Otherwise I feel vulnerability scanners would have picked this up in a 20 year span.

I know in the article this states that the hole is fixed in the next security release, but is there anyone with outside knowledge of the vulnerability know what changes were made to effectively close the hole? 


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 Enterprises are Attacking the Cybersecurity Problem
Concerns over supply chain vulnerabilities and attack visibility drove some significant changes in enterprise cybersecurity strategies over the past year. Dark Reading's 2021 Strategic Security Survey showed that many organizations are staying the course regarding the use of a mix of attack prevention and threat detection technologies and practices for dealing with cyber threats.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-3454
PUBLISHED: 2021-10-19
Truncated L2CAP K-frame causes assertion failure. Zephyr versions >= 2.4.0, >= v.2.50 contain Improper Handling of Length Parameter Inconsistency (CWE-130), Reachable Assertion (CWE-617). For more information, see https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-fx88-6c29-...
CVE-2021-3455
PUBLISHED: 2021-10-19
Disconnecting L2CAP channel right after invalid ATT request leads freeze. Zephyr versions >= 2.4.0, >= 2.5.0 contain Use After Free (CWE-416). For more information, see https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-7g38-3x9v-v7vp
CVE-2021-41150
PUBLISHED: 2021-10-19
Tough provides a set of Rust libraries and tools for using and generating the update framework (TUF) repositories. The tough library, prior to 0.12.0, does not properly sanitize delegated role names when caching a repository, or when loading a repository from the filesystem. When the repository is c...
CVE-2021-31378
PUBLISHED: 2021-10-19
In broadband environments, including but not limited to Enhanced Subscriber Management, (CHAP, PPP, DHCP, etc.), on Juniper Networks Junos OS devices where RADIUS servers are configured for managing subscriber access and a subscriber is logged in and then requests to logout, the subscriber may be fo...
CVE-2021-31379
PUBLISHED: 2021-10-19
An Incorrect Behavior Order vulnerability in the MAP-E automatic tunneling mechanism of Juniper Networks Junos OS allows an attacker to send certain malformed IPv4 or IPv6 packets to cause a Denial of Service (DoS) to the PFE on the device which is disabled as a result of the processing of these pac...