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.

Attacks/Breaches

12/21/2015
04:30 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

Yellow Alert Sounded For Juniper Vulns, Feds Called In

SANS ISC raises infosec alert level and FBI investigates potential nation-state activity leading to backdoor vulnerabilities in Juniper ScreenOS products.

The infosec alert level for the Internet Storm Center was bumped to yellow today on the heels of the announcement of two crucial vulnerabilities Juniper firewalls that rocked the infosec world last week. And as the industry scrambles to fill these gaping holes in its ScreenOS platform, news continues to trickle in that FBI officials are investigating potential nation-state actions that led to the insertion of an authentication backdoor that impacts tens of thousands of devices on the Internet.

Johannes Ullrich, director of the SANS ISC, said in a post this morning that the ISC decided to raise the alert level for three big reasons.

"Juniper devices are popular, and many organizations depend on them to defend their networks. The "backdoor" password is now known, and exploitation is trivial at this point," Ullrich wrote.  "With this week being a short week for many of us, addressing this issue today is critical."

As he warns security practitioners, there is very little that organizations can do to protect themselves from these vulnerabilities, particularly the one which allows attackers to decrypt VPN traffic. The backdoor vulnerability which requires that password to be activated--a point moot now that it is publicly known--but it can be countered by restricting access to SSH and telnet.

"Only administrative workstations should be able to connect to these systems via ssh, and nobody should be able to connect via telnet," he says. "This is "best practice" even without a backdoor."

Researchers with FoxIT initially reported finding the backdoor password within six hours of getting their hands on the Juniper patch. According to a post from HD Moore, chief research officer at Rapid7, the password  was chosen to look like other debug format strings in the code.

As he explains, the timing is interesting on these vulnerabilities as they were not present within versions of the software before 2013 releases.

"The authentication backdoor is not actually present in older versions of ScreenOS," Moore wrote. "The authentication backdoor did not seem to get added until a release in late 2013."

This could be another breadcrumb on the trail of investigators looking into how such a huge hole--one affecting over 26,000 devices according to a scan made by Moore--could have been inserted into the source code of such a prominent security product. According to a CNN report, the FBI is currently investigating the possibility that nation-state actors placed the backdoor for the purpose of espionage. Meanwhile, The Register reports an anonymous former Juniper employee who pointed to the fact that much of Juniper's "sustaining engineering" for ScreenOS is done in China.

 

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Edge-DRsplash-10-edge-articles
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
News
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Building the SOC of the Future
Building the SOC of the Future
Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-27132
PUBLISHED: 2021-02-27
SerComm AG Combo VD625 AGSOT_2.1.0 devices allow CRLF injection (for HTTP header injection) in the download function via the Content-Disposition header.
CVE-2021-25284
PUBLISHED: 2021-02-27
An issue was discovered in through SaltStack Salt before 3002.5. salt.modules.cmdmod can log credentials to the info or error log level.
CVE-2021-3144
PUBLISHED: 2021-02-27
In SaltStack Salt before 3002.5, eauth tokens can be used once after expiration. (They might be used to run command against the salt master or minions.)
CVE-2021-3148
PUBLISHED: 2021-02-27
An issue was discovered in SaltStack Salt before 3002.5. Sending crafted web requests to the Salt API can result in salt.utils.thin.gen_thin() command injection because of different handling of single versus double quotes. This is related to salt/utils/thin.py.
CVE-2021-3151
PUBLISHED: 2021-02-27
i-doit before 1.16.0 is affected by Stored Cross-Site Scripting (XSS) issues that could allow remote authenticated attackers to inject arbitrary web script or HTML via C__MONITORING__CONFIG__TITLE, SM2__C__MONITORING__CONFIG__TITLE, C__MONITORING__CONFIG__PATH, SM2__C__MONITORING__CONFIG__PATH, C__M...