title: Junos OS: In a scenario with dhcp-security and option-82 configured jdhcpd crashes upon receipt of a malformed DHCP packet
description: An Improper Validation of Syntactic Correctness of Input vulnerability in the Juniper DHCP daemon (jdhcpd) of Juniper Networks Junos OS allows an adjacent unauthenticated attacker sending a malformed DHCP packet to cause a crash of jdhcpd and thereby a Denial of Service (DoS). If option-82 is configured in a DHCP snooping / -security scenario, jdhcpd crashes if a specific malformed DHCP request packet is received. The DHCP functionality is impacted while jdhcpd restarts, and continued exploitation of the vulnerability will lead to the unavailability of the DHCP service and thereby a sustained DoS. This issue affects Juniper Networks Junos OS 13.2 version 13.2R1 and later 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.3R2-S7, 19.3R3-S4; 19.4 versions prior to 19.4R3-S6; 20.1 versions prior to 20.1R3-S3; 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-S1, 21.1R3; 21.2 versions prior to 21.2R1-S1, 21.2R2. This issue does not affect Juniper Networks Junos OS version 12.3R12 and prior versions.
problem types: CWE-1286 Improper Validation of Syntactic Correctness of Input
affected:
{
product: Junos OS
vendor: Juniper Networks
versions:
lessThan: 15.1R7-S11, status: affected, version: unspecified, versionType: custom
lessThanOrEqual: 12.3R12, status: unaffected, version: unspecified, versionType: custom
lessThan: 13.2*, status: affected, version: 13.2R1, versionType: custom
lessThan: 18.3R3-S6, status: affected, version: 18.3, versionType: custom
lessThan: 18.4R2-S9, 18.4R3-S10, status: affected, version: 18.4, versionType: custom
lessThan: 19.1R2-S3, 19.1R3-S7, status: affected, version: 19.1, versionType: custom
lessThan: 19.2R1-S8, 19.2R3-S4, status: affected, version: 19.2, versionType: custom
lessThan: 19.3R2-S7, 19.3R3-S4, status: affected, version: 19.3, versionType: custom
lessThan: 19.4R3-S6, status: affected, version: 19.4, versionType: custom
lessThan: 20.1R3-S3, status: affected, version: 20.1, versionType: custom
lessThan: 20.2R3-S3, status: affected, version: 20.2, versionType: custom
lessThan: 20.3R3-S1, status: affected, version: 20.3, versionType: custom
lessThan: 20.4R3, status: affected, version: 20.4, versionType: custom
lessThan: 21.1R2-S1, 21.1R3, status: affected, version: 21.1, versionType: custom
lessThan: 21.2R1-S1, 21.2R2, status: affected, version: 21.2, versionType: custom
}
metrics:
cvssV3_1: [
attackComplexity: LOW
attackVector: ADJACENT_NETWORK
availabilityImpact: HIGH
baseScore: 7.4
baseSeverity: HIGH
confidentialityImpact: NONE
integrityImpact: NONE
privilegesRequired: NONE
scope: CHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
version: 3.1
]
exploits: Juniper SIRT is not aware of any malicious exploitation of this vulnerability.
solutions: The following software releases have been updated to resolve this specific issue: 15.1R7-S11, 18.3R3-S6, 18.4R2-S9, 18.4R3-S10, 19.1R2-S3, 19.1R3-S7, 19.2R1-S8, 19.2R3-S4, 19.3R2-S7, 19.3R3-S4, 19.4R3-S6, 20.1R3-S3, 20.2R3-S3, 20.3R3-S1, 20.4R3, 21.1R2-S1, 21.1R3, 21.2R1-S1, 21.2R2, 21.3R1, and all subsequent releases.
workarounds: There are no known workarounds for this issue.