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

10/12/2018
08:05 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

DHS Raps Juniper Over the Knuckles for 40 Junos OS Vulnerabilities

The Department of Homeland Security felt it necessary to take Juniper Networks to the woodshed for 40 vulnerabilities, many critical, that affected the company's Junos OS.

The Department of Homeland Security took Juniper Networks out to the woodshed this week, and gave the company a couple of major whacks across the knuckles.

If one follows the links in the polite email the DHS sent out about Juniper software, they would find about 40 newly revealed security vulnerabilities that affect Junos OS listed. That's the OS that runs all the network hardware that Juniper sells.

Juniper hardware is usually enterprise-grade, as are their customers. But having this large amount of problems all hit at once may cause some questioning about the validity of the network services that Juniper offers as well.

One critical vulnerability -- Level 9.8 -- was found in the Network Time Protocol (NTP) area. It's flagged as CVE-2016-1549, CVE-2018-7170, CVE-2018-7182, CVE-2018-7184, CVE-2018-7185, and CVE-2018-7183 at cve.mitre.org for all the different Junos OS versions that were affected.

What this means is that the NTP daemon (NTPD) in NTP 4.2.8p4 before 4.2.8p11 will drop bad packets before updating the "received" timestamp, which allows remote attackers to cause a denial of service disruption by sending a packet with a zero-origin timestamp. That causes the association to reset and setting the contents of the packet as the most recent timestamp.

Now, standard best practices such as control plane firewall filters, edge filtering and access lists will protect against remote malicious attacks against NTP. But not every connection has hardware protection around it.

Other kinds of higher-level vulnerabilities were in the list as well.

A persistent cross-site scripting vulnerability (CVE-2018-0047) in the UI framework used by Junos Space Security Director -- a security administrator control program -- may allow already authenticated users to inject persistent and malicious scripts. It has a CVSS rating of 8, and a high-risk level. If exploited, it can allow stealing of information or performing actions as a different user when other users access the Security Director web interface.

Oh yeah, there is also remote root access for a device in the mix. Surprise. CVE-2018-0052 outlines how it can happen.

If the remote shell (RSH) service is enabled on Junos OS and if the privileged account management (PAM) authentication is disabled, a remote unauthenticated attacker can obtain root access to the device.

RSH service is disabled by default on Junos. There is no documented command-line interface (CLI) command to enable this service. However, an undocumented CLI command -- since removed along with the entire CLI package -- allows a privileged Junos user to enable RSH service and disable PAM, and hence expose the system to unauthenticated root access.

While all of the mess is supposed to be fixed by patching, doing this much patching at once is a real problem for enterprises. These are critical vulnerabilities that need to be eliminated, but there is a lot of online production that is happening with the affected servers. It's not a simple thing to do so wide and deep a patch on production environments.

But Juniper did get rapped for making it necessary.

Related posts:

— 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
When It Comes To Security Tools, More Isn't More
Lamont Orange, Chief Information Security Officer at Netskope,  1/11/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2020: The Year in Security
Download this Tech Digest for a look at the biggest security stories that - so far - have shaped a very strange and stressful year.
Flash Poll
Assessing Cybersecurity Risk in Today's Enterprises
Assessing Cybersecurity Risk in Today's Enterprises
COVID-19 has created a new IT paradigm in the enterprise -- and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-16961
PUBLISHED: 2021-01-15
SolarWinds Web Help Desk 12.7.0 allows XSS via a Schedule Name.
CVE-2020-35733
PUBLISHED: 2021-01-15
An issue was discovered in Erlang/OTP before 23.2.2. The ssl application 10.2 accepts and trusts an invalid X.509 certificate chain to a trusted root Certification Authority.
CVE-2021-23836
PUBLISHED: 2021-01-15
An issue was discovered in flatCore before 2.0.0 build 139. A stored XSS vulnerability was identified in the prefs_smtp_psw HTTP request body parameter for the acp interface. An admin user can inject malicious client-side script into the affected parameter without any form of input sanitization. The...
CVE-2021-23837
PUBLISHED: 2021-01-15
An issue was discovered in flatCore before 2.0.0 build 139. A time-based blind SQL injection was identified in the selected_folder HTTP request body parameter for the acp interface. The affected parameter (which retrieves the file contents of the specified folder) was found to be accepting malicious...
CVE-2021-23838
PUBLISHED: 2021-01-15
An issue was discovered in flatCore before 2.0.0 build 139. A reflected XSS vulnerability was identified in the media_filter HTTP request body parameter for the acp interface. The affected parameter accepts malicious client-side script without proper input sanitization. For example, a malicious user...