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

rpd core after receiving invalid LDP OID value in SNMP query

0

0

Article ID: JSA10455 SECURITY_ADVISORIES Last Updated: 09 May 2013Version: 1.0
Legacy Advisory Id:
PSN-2010-10-966
Product Affected:
This issue affects all routers running Junos 10.0 and above with SNMP enabled. The issue specifically requires read access via SNMP, which is typically only permitted from trusted IP networks.
Problem:

During internal conformance testing, an invalid SNMP getnext request for an LDP OID caused the rpd process to crash. The issue was found to be caused by an invalid OID value in the SNMP query. It's important to note that LDP must be enabled for this crash to occur.
Solution:

Additional checks for validity of SNMP queries were added to the Junos network operating system. Junos now rejects illegal OID values in the LDP SNMP agent.

All JUNOS software releases built on or after 06-August-2010 have fixed this specific issue. Releases containing the fix specifically include: 10.0S7.1, 10.1S6.2, 10.2R2 and all subsequent releases (i.e. all releases built after 10.2R2). Junos releases prior to 10.0 are unaffected by this vulnerability.

This issue is being tracked as PR 530348. While this PR is not viewable by customers, it can be used as a reference when discussing the issue with JTAC.

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.

Workaround:

The primary requirement for exploiting this vulnerability is having direct, authenticated SNMP read access to the router. Best Common Practices dictate that SNMP access to networking devices be permitted from trusted IP networks through the use of authentication (eg. SNMP community strings), edge filtering, and/or control plane filtering. While the CVSS Base Score is relatively high, factoring in the environmental attributes for a typical network installation completely mitigates the risk associated with this issue.
Implementation:

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:
7.8 (AV:N/AC:L/Au:N/C:N/I:N/A:C/E:P/RL:O/RC:C)
Severity Level:
High
Severity Assessment:
CVSS Environmental Score: 0 (AV:N/AC:L/Au:N/C:N/I:N/A:C/E:P/RL:O/RC:C/CDP:LM/TD:N/CR:ND/IR:ND/AR:ND)

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