m2pc writes: Ars Technica reports that Juniper Networks firewalls have been discovered to include “unauthorized code” inserted into their ScreenOS software. Juniper has has published an advisory addressing the matter, with instructions to patch the affected devices. From the Ars article: “NetScreen firewalls using ScreenOS 6.2.0r15 through 6.2.0r18 and 6.3.0r12 through 6.3.0r20 are affected and require immediate patching. Release notes published by Juniper suggest the earliest vulnerable versions date back to at least 2012 and possibly earlier. … The first flaw allows unauthorized remote administrative access to an affected device over SSH or telnet. Exploits can lead to complete compromise. ‘The second issue may allow a knowledgeable attacker who can monitor VPN traffic to decrypt that traffic, ‘ the advisory said.” The rogue code was discovered during a recent internal source code review conducted by Juniper. Read more of this story at Slashdot.
View original post here:
‘Unauthorized Code’ In Juniper Firewalls Could Decrypt VPN Traffic
jjslash writes: For a few years now, Intel CPU overclocking has been limited to more expensive Core i5 and Core i7 ‘K’ processors. Skylake launched this year with the rumor of strong non-K processor overclocking through an adjustable base clock, but that never eventuated… until now. In overclocking circles it was rumored that BCLK (base clock) overclocking might become a possibility in Skylake processors, but it would be up to motherboard manufacturers to circumvent Intel’s restrictions. Asrock, Asus and a few other motherboard manufacturers are said to be issuing a BIOS update soon that will unlock base clock overclocking on Z170 motherboards. TechSpot has got an early look, overclocking a locked Core i3-6100 to 4.7GHz on air cooling. Read more of this story at Slashdot. 
An anonymous reader writes: Basic ASLR was not implemented in 3 major antivirus makers, allowing attackers to use the antivirus itself towards attacking Windows PCs. The bug, in layman terms, is: the antivirus would select the same memory address space every time it would run. If attackers found out the memory space’s address, they could tell their malicious code to execute in the same space, at the same time, and have it execute with root privileges, which most antivirus have on Windows PCs. It’s a basic requirement these days for software programmers to use ASLR (Address Space Layout Randomization) to prevent their code from executing in predictable locations. Affected products: AVG, McAfee, Kaspersky. All “quietly” issued fixes. Read more of this story at Slashdot.