CVE-2023-28964 - Improper Handling of Length Parameter Inconsistency

Severity

75%

Complexity

39%

Confidentiality

60%

An Improper Handling of Length Parameter Inconsistency vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows a network based, unauthenticated attacker to cause an RPD crash leading to a Denial of Service (DoS). Continued receipt and processing of this packet will create a sustained Denial of Service (DoS) condition. Upon receipt of a malformed BGP flowspec update, RPD will crash resulting in a Denial of Service. This issue affects Juniper Networks Junos OS: All versions prior to 18.1R3-S11; 18.2 versions prior to 18.2R3-S6; 18.3 versions prior to 18.3R3-S4; 18.4 versions prior to 18.4R3-S6; 19.1 versions prior to 19.1R3-S4; 19.2 versions prior to 19.2R3-S1; 19.3 versions prior to 19.3R3-S1; 19.4 versions prior to 19.4R3; 20.1 versions prior to 20.1R2; 20.2 versions prior to 20.2R2; 20.3 versions prior to 20.3R1-S1, 20.3R2; Juniper Networks Junos OS Evolved: All versions prior to 20.1R3-EVO; 20.2 versions prior to 20.2R2-EVO; 20.3 versions prior to 20.3R2-EVO;

CVSS 3.1 Base Score 7.5. CVSS Attack Vector: network. CVSS Attack Complexity: low. CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Demo Examples

Improper Handling of Length Parameter Inconsistency

CWE-130

In the following C/C++ example the method processMessageFromSocket() will get a message from a socket, placed into a buffer, and will parse the contents of the buffer into a structure that contains the message length and the message body. A for loop is used to copy the message body into a local character string which will be passed to another method for processing.


               
}
return success;// get message from socket and store into buffer//Ignoring possibliity that buffer > BUFFER_SIZE
success = processMessage(message);// place contents of the buffer into message structure// copy message body into string for processing
message[index] = msg->msgBody[index];
// process message

However, the message length variable from the structure is used as the condition for ending the for loop without validating that the message length variable accurately reflects the length of message body. This can result in a buffer over read by reading from memory beyond the bounds of the buffer if the message length variable indicates a length that is longer than the size of a message body (CWE-130).

Overview

Type

Juniper

First reported 1 year ago

2023-04-17 22:15:00

Last updated 1 year ago

2023-04-27 18:11:00

Affected Software

Juniper JUNOS 18.1 R3

18.1

Juniper JUNOS 18.1R2

18.1

Juniper JUNOS 18.2

18.2

Juniper JUNOS 18.2 R2-S1

18.2

Juniper JUNOS 18.2R2-S2

18.2

Juniper JunOS 18.2 R1-S3

18.2

Juniper JUNOS 18.3 R1-S1

18.3

Juniper JUNOS 18.3 R2

18.3

Juniper JUNOS 18.3 R1

18.3

Juniper JUNOS R2-S2

18.1

Juniper JunOS 18.4 R1

18.4

Juniper JUNOS 18.1R3-S4

18.1

Juniper JUNOS 18.1 R3-S3

18.1

Juniper JUNOS 18.1 R3-S2

18.1

Juniper JUNOS 18.1

18.1

Juniper JUNOS R2-S1

18.1

Juniper JUNOS 18.1 R2-S4

18.1

Juniper JUNOS 18.3 R1-S2

18.3

Juniper JUNOS 18.3

18.3

Juniper JUNOS 18.4

18.4

Juniper JunOS 18.1 R3-s1

18.1

Juniper JunOS 18.2 R1

18.2

Juniper Junos OS 18.4 R1-S1

18.4

Juniper JUNOS 18.3R1-S3

18.3

Juniper JUNOS 18.2R2-S3

18.2

Juniper JUNOS18.2 R2-S4

18.2

Juniper JUNOS 18.2 R1-S5

18.2

Juniper JUNOS 18.4R1-S2

18.4

Juniper Junos OS 19.1 R1

19.1

Juniper Junos OS 19.1

19.1

Juniper Junos OS 19.2 R1

19.2

Juniper JUNOS 18.4R2

18.4

Juniper JUNOS 18.2R3

18.2

Juniper JUNOS 18.1 R3-S6

18.1

Juniper JUNOS 18.1 R3-S7

18.1

Juniper Junos OS 19.1 R1-s1

19.1

Juniper JUNOS 19.1 R1-S3

19.1

Juniper JUNOS 19.1 R1-S2

19.1

Juniper JUNOS 18.2 R2-S5

18.2

Juniper JUNOS 18.2 R2-S6

18.2

Juniper JUNOS 18.4 R1-S5

18.4

Juniper JUNOS 19.2 R1-S1

19.2

Juniper JUNOS 19.2 R1-S2

19.2

Juniper JUNOS 18.3 R1-S5

18.3

Juniper JUNOS 18.2 R3-S1

18.2

Juniper JUNOS 18.3 R2-S1

18.3

Juniper JUNOS 18.3 R2-S2

18.3

Juniper JUNOS 18.4 R2-S1

18.4

Juniper JUNOS 19.3

19.3

Juniper JUNOS 19.3 R1

19.3

Juniper Junos OS 19.2

19.2

Juniper JUNOS 18.4 R2-S2

18.4

Juniper JUNOS 18.3 R1-S6

18.3

Juniper JUNOS 18.2 R3-S2

18.2

Juniper JUNOS 18.1 R3-S8

18.1

Juniper JUNOS 19.2 R1-S3

19.2

Juniper JUNOS 18.3 R3

18.3

Juniper JUNOS 19.4 R1

19.4

Juniper JUNOS 19.3 R2

19.3

Juniper Junos OS 19.1 R2

19.1

Juniper JUNOS 18.4 R3

18.4

Juniper JUNOS 18.4 R2-S3

18.4

Juniper JUNOS 18.3 R3-S1

18.3

Juniper JUNOS 18.1 R3-S9

18.1

Juniper JUNOS 19.3 R2-S1

19.3

Juniper JUNOS 19.3 R1-S1

19.3

Juniper JUNOS 20.1 R1

20.1

Juniper JUNOS 19.4 R1-S1

19.4

Juniper JUNOS 19.3 R2-S2

19.3

Juniper JUNOS 19.1 R1-S4

19.1

Juniper JUNOS 18.4 R1-S6

18.4

Juniper JUNOS 18.3 R2-S3

18.3

Juniper JUNOS 18.2 R3-S3

18.2

Juniper JUNOS

Stay updated

ExploitPedia is constantly evolving. Sign up to receive a notification when we release additional functionality.

Get in touch

If you'd like to report a bug or have any suggestions for improvements then please do get in touch with us using this form. We will get back to you as soon as we can.