Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

2012-07 Security Bulletin: Junos: Inbound management traffic is allowed even though 'host-inbound-traffic' is not configured to allow it



Article ID: JSA10525 SECURITY_ADVISORIES Last Updated: 09 May 2013Version: 2.0
Legacy Advisory Id:
Product Affected:
This issue can affect all SRX Series services gateways configured with a security-zone screen to limit access to host inbound traffic.

Inbound "to-self" management traffic (eg. ssh, telnet, ping, etc.) is accepted by the device even though the service is not explicitly included in the 'host-inbound-traffic' configuration for the ingress interface within the security-zone. For example:
security-zone UNTRUSTED {
    address-book {
        address fafc-;
        address host-;
    screen untrusted-screen;
    interfaces {
        reth1.10 {
            host-inbound-traffic {
                system-services {
In the sample configuration above, only traceroute and ping should be allowed, but SSH is also allowed on the interface.

The issue only occurs if the destination IP address exists on another interface on a different VR.

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

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

The destined interface was not correctly identified due to an incorrect destination route-table ID. After performing a routing lookup, even though the packet is routed to-self, the flow handled it like a pass-through packet, which is normally permitted by the default to-self policy.

All Junos OS software releases built on or after 2012-06-21 have fixed this specific issue. Releases containing the fix specifically include: 10.4R10, 11.2R7, 11.4R4, 12.1R2-S1, 12.1R3 and all subsequent releases (i.e. all releases built after 12.1R3).

This issue is being tracked as PR 754392 and is visible on the Customer Support website.

KB16765 - "In which releases are vulnerabilities fixed?" describes which release vulnerabilities are fixed as per our End of Engineering and End of Life support policies.


No known workaround exists for this issue.

How to obtain fixed software:

Security vulnerabilities in Junos are fixed in the next available Maintenance Release of each supported Junos version. In some cases, a Maintenance Release is not planned to be available in an appropriate time-frame. For these cases, Service Releases are made available in order to be more timely. Security Advisory and Security Notices will indicate which Maintenance and Service Releases contain fixes for the issues described. Upon request to JTAC, customers will be provided download instructions for a Service Release. Although Juniper does not provide formal Release Note documentation for a Service Release, a list of "PRs fixed" can be provided on request.
CVSS Score:
6.8 (AV:N/AC:L/Au:S/C:C/I:N/A:N)
Severity Level:
Severity Assessment:
Information for how Juniper Networks uses CVSS can be found at KB 16446 "Common Vulnerability Scoring System (CVSS) and Juniper's Security Advisories."

Related Links

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search