CVE-2022-22177

Summary

A release of illegal memory vulnerability in the snmpd daemon of Juniper Networks Junos OS, Junos OS Evolved allows an attacker to halt the snmpd daemon causing a sustained Denial of Service (DoS) to the service until it is manually restarted. This issue impacts any version of SNMP – v1,v2, v3 This issue affects: Juniper Networks Junos OS 12.3 versions prior to 12.3R12-S20; 15.1 versions prior to 15.1R7-S11; 18.3 versions prior to 18.3R3-S6; 18.4 versions prior to 18.4R2-S9, 18.4R3-S10; 19.1 versions prior to 19.1R2-S3, 19.1R3-S7; 19.2 versions prior to 19.2R1-S8, 19.2R3-S4; 19.3 versions prior to 19.3R3-S4; 19.4 versions prior to 19.4R2-S5, 19.4R3-S6; 20.1 versions prior to 20.1R3-S2; 20.2 versions prior to 20.2R3-S3; 20.3 versions prior to 20.3R3-S1; 20.4 versions prior to 20.4R3; 21.1 versions prior to 21.1R2-S2, 21.1R3; 21.2 versions prior to 21.2R1-S2, 21.2R2. Juniper Networks Junos OS Evolved 21.2 versions prior to 21.2R3-EVO; 21.3 versions prior to 21.3R2-EVO.

Affected Software

VendorProductVersion RangeStatus
Juniper NetworksJunos OS12.3 < 12.3R12-S20affected
Juniper NetworksJunos OS15.1 < 15.1R7-S11affected
Juniper NetworksJunos OS18.3 < 18.3R3-S6affected
Juniper NetworksJunos OS18.4 < 18.4R2-S9, 18.4R3-S10affected
Juniper NetworksJunos OS19.1 < 19.1R2-S3, 19.1R3-S7affected
Juniper NetworksJunos OS19.2 < 19.2R1-S8, 19.2R3-S4affected
Juniper NetworksJunos OS19.3 < 19.3R3-S4affected
Juniper NetworksJunos OS19.4 < 19.4R2-S5, 19.4R3-S6affected
Juniper NetworksJunos OS20.1 < 20.1R3-S2affected
Juniper NetworksJunos OS20.2 < 20.2R3-S3affected
Juniper NetworksJunos OS20.3 < 20.3R3-S1affected
Juniper NetworksJunos OS20.4 < 20.4R3affected
Juniper NetworksJunos OS21.1 < 21.1R2-S2, 21.1R3affected
Juniper NetworksJunos OS21.2 < 21.2R1-S2, 21.2R2affected
Juniper NetworksJunos OS Evolvedunspecified < 21.2R3-EVOaffected
Juniper NetworksJunos OS Evolved21.3 < 21.3R2-EVOaffected

Weaknesses

  • Release of illegal memory
  • Denial of Service (DoS)
  • CWE-755: CWE-755 Improper Handling of Exceptional Conditions

Workarounds

There are no workarounds for this issue.

For V1, V2 you can reduce the risk of exploitation by configuring the client-list to limit access to network management system (NMS) machines.

See the Network Management and Monitoring Guide for further instructions.

example:

[snmp client-list client-list-name "ip-addresses";]

For V3 you can reduce the risk of exploitation by configuring SNMP security to trusted devices only.

For any release of SNMP you can reduce the risk of exploitation by implementing source and destination IP filter rules as well as using Read Only communities where possible.

Regardless of these risk reduction methods, an attacker able to spoof trusted IP addresses can send the attack to an exposed and reachable SNMP RW community.

ADP Enrichment

CVE Program Container

Additional References

References