CVE-2022-22237 An attacker can compromise Junos OS confidentiality or integrity by attacking the kernel.
This issue has been assigned the CVE identifier CVE-2019-3377. A network-based attacker can exploit this vulnerability to spoof BGP or LDP sessions. An attacker can send crafted BGP or LDP packets to an affected device that appear as though they have come from a trusted peer and create a BGP or LDP session. This could be exploited by spoofed BGP or LDP messages to route traffic through a malicious peer. A network-based attacker can exploit this vulnerability to spoof BGP or LDP sessions. An attacker can send crafted BGP or LDP packets to an affected device that appear as though they have come from a trusted peer and create a BGP or LDP session. This could be exploited by spoofed BGP or LDP messages to route traffic through a malicious peer. An attacker can also spoof the IP address of the remote peer. This could be exploited by spoofed BGP or LDP messages to route traffic through a malicious peer. An attacker can also spoof the IP address of the remote peer. An attacker can exploit this vulnerability to spoof BGP or LDP sessions. An attacker can send crafted BGP or LDP packets to an affected device that appear as though they have come from a trusted peer and create a BGP or LVD session. This could be exploited by spoofed BGP or LDP messages to route traffic through a malicious peer. An attacker can exploit this vulnerability to spoof BGP or LDP sessions. An
BGP and LDP Protocol Deficiencies
BGP and LDP are protocol deficiencies in the IETF RFCs that describe the routing protocols.
BGP was specified in RFC 4271, which is a router-to-router protocol with extensions for autodiscovery and remote configuration. LDP was specified in RFC 5036, which is a label distribution protocol used to set up point-to-point links or multipoint point-to-multipoint links using BGP for its routing information exchange mechanism.
BGPv6
: The Future of BGP
BGPv6 is the new, modernized version of Border Gateway Protocol (BGP) as found in RFC4271. In November 2015, it was adapted and implemented into the next-generation IETF standards track. The standard update to BGPv6 is expected to become a formal standard in 2019.
Current implementations of BDPv6 include Cisco’s BGPv6 and Huawei’s V5R1, which is used in its Ax100 devices. This is a good sign that BDPv6 will be widely adopted soon. But it should be noted that while almost all vendors are currently implementing or adopting BDPv6, there still remains many unknowns about how the protocol will function with other vendors who haven’t yet made the switch.
Timeline
Published on: 10/18/2022 03:15:00 UTC
Last modified on: 10/20/2022 14:58:00 UTC