7.5 High
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
NONE
Integrity Impact
NONE
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
6.7 Medium
AI Score
Confidence
High
0.003 Low
EPSS
Percentile
65.6%
Multiple BGP implementations have been identified as vulnerable to specially crafted Path Attributes of a BGP UPDATE. Instead of ignoring invalid updates they reset the underlying TCP connection for the BGP session and de-peer the router.
> This is undesirable because a session reset impacts not only routes with the BGP UPDATE but also the other valid routes exchanged over the session. RFC 7606 Introduction
The Border Gateway Protocol (BGP, RFC 4271) is a widely used inter-Autonomous System routing protocol. BGP communication among peer routers is critical to the stable operation of the Internet. A number of known BGP security issues were addressed in RFC 7606 Revised Error Handling for BGP UPDATE Messages in 2015.
Recent reports indicate that multiple BGP implementations do not properly handle specially crafted Path Attributes in the BGP UPDATE messages. An attacker with a valid, configured BGP session could inject a specially crafted packet into an existing BGP session or the underlying TCP session (179/tcp). A vulnerable BGP implementation could drop sessions when processing crafted UPDATE messages. A persistent attack could lead to routing instability (route flapping).
This vulnerability was first announced as affecting OpenBSD based routers. Further investigation indicates that other vendors are affected by the same or similar issues. Please see the Systems Affected section below. Here are the CVE IDs that were reserved by the reporter for different vendors that were tested:
A remote attacker could publish a BGP UPDATE with a crafted set of Path Attributes, causing vulnerable routers to de-peer from any link from which such an update were received. Unaffected routers might also pass the crafted updates across the network, potentially leading to the update arriving at an affected router from multiple sources, causing multiple links to fail.
The CERT/CC is currently unaware of a practical solutions for every vendor but some of the vendors allow you to change the response to errors in BGP path updates. Networks using appliances from Juniper and Nokia can mitigate this behavior by enabling:
(Juniper)
set protocols bgp bgp-error-tolerance
(Nokia)
[router bgp group]
error-handling update-fault-tolerance
Thanks to the reporter Ben Cartwright-Cox. This document was written by Timur Snoke.
347067
Filter by status: All Affected Not Affected Unknown
Filter by content: __ Additional information available
__ Sort by: Status Alphabetical
Expand all
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: July 31, 2023
VU#347067.1 | Affected |
---|
23-0731 D-Link US SIRT :: [email protected]
For owners of D-Link SKUs the affected model list with fixes under development:
NOT affected models that associate with affected solutions: 5. DXS-3400 All Hardware revision not affected
Model affected, however have work-around to avoid issue 6. DXS-5000 Hardware Revision A1 7. DQS-5000 Hardware Revision A1 Workaround temporally solution :
a) Provide filter or restricted settings for attributes in BGP UPDATE
b) filter-list : filter-list as-path-list-number {in | out} / no filter-list as-path-list-number {in | out}
c) neighbor filter-list: neighbor {ipv4-address | ipv6-address} filter-list as-path-list-number {in | out} / no neighbor {ipv4-address | ipv6-address} filter-list as-path-list-number {in | out}
d) bgp maxas-limit: bgp maxas-limit number / no bgp maxas-limit
e) timers policy-apply delay, timers policy-apply delay delay / no timers policy-apply delay
Notified: 2023-07-12 Updated: 2023-11-16
Statement Date: November 16, 2023
VU#347067.1 | Affected |
---|
F5 BIG-IP products are affected thru vulnerable component ZebOS bgpd from IP Infusion. F5 published K000137315: ZebOS BGP vulnerability CVE-2023-45886, https://my.f5.com/manage/s/article/K000137315. CVE-2023-45886 was requested by F5 from MITRE as IP Infusion is not a CNA.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: August 29, 2023
VU#347067.1 | Affected |
---|
Please visit:
https://kb.juniper.net/JSA72510
Customers are advised to immediately implement BGP error tolerance by way of: [ protocols bgp bgp-error-tolerance … ]
Additional details can be found at https://www.juniper.net/documentation/us/en/software/junos/bgp/topics/topic-map/bgp-error-messages.html
Juniper considers configuring this option to be a Best Common Practice (BCP) as it not only prevents this issue from happening, but protects against similar issues as well.
Notified: 2023-07-12 Updated: 2023-09-15
Statement Date: September 14, 2023
VU#347067.1 | Affected |
---|
https://security.paloaltonetworks.com/CVE-2023-38802
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: July 12, 2023
VU#347067.1 | Affected |
---|
Red Hat Enterprise Linux is affected because the affected package (frr) is shipped on RHEL.
Systems not running frr as a BGP router are not vulnerable to this CVE.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: July 19, 2023
VU#347067.1 | Affected |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: August 28, 2023
VU#347067.1 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: July 12, 2023
VU#347067.1 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: August 02, 2023
VU#347067.1 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: July 12, 2023
VU#347067.1 | Not Affected |
---|
No BGP support in AVM’s home routers.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: August 01, 2023
VU#347067.1 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: July 12, 2023
VU#347067.1 | Not Affected |
---|
No Brocade Fibre Channel Products from Broadcom is affected.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: August 30, 2023
VU#347067.1 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: August 28, 2023
VU#347067.1 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: August 07, 2023
VU#347067.1 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: August 28, 2023
VU#347067.1 | Not Affected |
---|
Extreme follows RFC 4271 and does not implement RFC 7606. Since we perform as per our claimed RFC compliance, there is no vulnerability as the customer does not expect RFC 7606 behavior. We do not view this as a vulnerability, but rather, an issue of RFC compliance. There is no incorrect length handling issue.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: July 18, 2023
VU#347067.1 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: July 18, 2023
VU#347067.1 | Not Affected |
---|
The FreeBSD Project does not include a BGP implementation with the base system. However, users can install third-party BGP implementations from binary packages or the ports tree. These may be affected.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: July 12, 2023
VU#347067.1 | Not Affected |
---|
HardenedBSD does not ship with a BGP daemon in base. However, the ports tree does contain affected projects. Given the lack of BGP support in base, the HardenedBSD project is marked as unaffected.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: July 12, 2023
VU#347067.1 | Not Affected |
---|
illumos has no BGP, and expects its users to pull from their distro or other sources. illumos will advise distros to update their BGP IF they have one.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: July 17, 2023
VU#347067.1 | Not Affected |
---|
Intel is not impacted by this issue in either our products or company infrastructure.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: July 13, 2023
VU#347067.1 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: September 01, 2023
VU#347067.1 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: July 12, 2023
VU#347067.1 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: July 17, 2023
VU#347067.1 | Not Affected |
---|
Muonics has no products implementing BGP at this time.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: July 18, 2023
VU#347067.1 | Not Affected |
---|
NetBSD doesn’t come with any BGP software.
Some third-party BGP software may be available in pkgsrc, like quagga, and that software may be affected.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: August 22, 2023
VU#347067.1 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: July 13, 2023
VU#347067.1 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: July 14, 2023
VU#347067.1 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: July 13, 2023
VU#347067.1 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: July 12, 2023
VU#347067.1 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: July 21, 2023
VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-08-31 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: August 29, 2023
VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-08-04 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12
Statement Date: July 12, 2023
VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2023-07-12 Updated: 2023-09-12 VU#347067.1 | Unknown |
---|
We have not received a statement from the vendor.
View all 106 vendors __View less vendors __
API URL: | VINCE JSON | CSAF
—|—
Date Public: | 2023-09-12 Date First Published:| 2023-09-12 **Date Last Updated: **| 2023-11-16 14:03 UTC **Document Revision: ** | 3
tools.ietf.org/html/rfc4271
tools.ietf.org/html/rfc7606
blog.benjojo.co.uk/post/bgp-path-attributes-grave-error-handling
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-38283
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-38802
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40457
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-4481
ftp.openbsd.org/pub/OpenBSD/patches/7.3/common/006_bgpd.patch.sig
github.com/FRRouting/frr/pull/14290
kb.juniper.net/JSA72510
7.5 High
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
NONE
Integrity Impact
NONE
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
6.7 Medium
AI Score
Confidence
High
0.003 Low
EPSS
Percentile
65.6%