When xnm-ssl or xnm-clear-text is enabled within the [edit system services] hierarchy level of the Junos configuration, an unauthenticated, remote user could exploit the XNM command processor to consume excessive amounts of memory. This, in turn, could lead to system instability or other performance issues.

This issue was found during internal product security testing.

Juniper SIRT is not aware of any malicious exploitation of this vulnerability.

No other Juniper Networks products or platforms are affected by this issue.

This issue has been assigned CVE-2014-0613 .

The following software releases have been updated to resolve this specific issue:

• All Junos OS software releases built on or after 2013-12-17, or
• Junos OS 10.4R16, 11.4R10, 12.1R8-S2, 12.1X44-D30, 12.1X45-D20, 12.1X46-D10, 12.2R7, 12.3R5, 13.1R3-S1, 13.2R2-S2, 13.3R1, and all subsequent releases (i.e. all releases built after 13.3R1).

Use access lists or firewall filters to limit access to the router via the Junos XML protocol only from trusted hosts.

In addition to the recommendations listed above, it is good security practice to limit the exploitable attack surface of critical infrastructure networking equipment. Use additional access lists or firewall filters to limit access to the router via ssh or telnet only from trusted, administrative networks or hosts.

• Configuring clear-text or SSL Service for Junos XML protocol Client Applications
• KB16613: Overview of the Juniper Networks SIRT Monthly Security Bulletin Publication Process [juniper.net]
• KB16765: In which releases are vulnerabilities fixed? [juniper.net]
• KB16446: Common Vulnerability Scoring System (CVSS) and Juniper's Security Advisories [juniper.net]
• Report a Vulnerability - How to Contact the Juniper Networks Security Incident Response Team
• CVE-2014-0613: Memory-consumption DoS attack possible when xnm-ssl or xnm-clear-text service enabled