Arista 7280R3/7500R3/7800R3 up to 4.22.1F/4.23.14M/4.24.11M/4.25.0F VXLAN buffer overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Arista 7280R3, 7500R3 and 7800R3 up to 4.22.1F/4.23.14M/4.24.11M/4.25.0F. It has been rated as critical. Affected by this issue is some unknown functionality of the component VXLAN. Performing a manipulation results in buffer overflow. This vulnerability is cataloged as CVE-2023-24548. The attack must originate from the local network. There is no exploit available. Upgrading the affected component is advised.
Details
A vulnerability, which was classified as problematic, was found in Arista 7280R3, 7500R3 and 7800R3 up to 4.22.1F/4.23.14M/4.24.11M/4.25.0F. This affects an unknown function of the component VXLAN. The manipulation with an unknown input leads to a buffer overflow vulnerability. CWE is classifying the issue as CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. This is going to have an impact on availability.
The weakness was shared 08/24/2023 as Security Advisory 0089 / Bug 828687 as confirmed security advisory (Website). The advisory is shared at arista.com. This vulnerability is uniquely identified as CVE-2023-24548. Neither technical details nor an exploit are publicly available. The advisory points out:
On affected platforms running Arista EOS with VXLAN configured, malformed or truncated packets received over a VXLAN tunnel and forwarded in hardware can cause egress ports to be unable to forward packets. The device will continue to be susceptible to the issue until remediation is in place.
Upgrading to version 4.25.1F, 4.26.0F, 4.27.0F, 4.28.0F, 4.29.0F or 4.30.0F eliminates this vulnerability. The security advisory contains the following remark:
There is no known mitigation for the issue. The recommended resolution is to upgrade to a remediated software version at your earliest convenience.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 5.0
VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Arista): 5.3
Vendor Vector (Arista): 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CNA Base Score: 5.3
CNA Vector (Arista Networks, Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Buffer overflowCWE: CWE-120 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: 7280R3/7500R3/7800R3 4.25.1F/4.26.0F/4.27.0F/4.28.0F/4.29.0F/4.30.0F
Timeline
01/26/2023 🔍08/24/2023 🔍
08/24/2023 🔍
09/16/2023 🔍
Sources
Advisory: Security Advisory 0089 / Bug 828687Status: Confirmed
CVE: CVE-2023-24548 (🔍)
GCVE (CVE): GCVE-0-2023-24548
GCVE (VulDB): GCVE-100-237909
Entry
Created: 08/24/2023 14:10Updated: 09/16/2023 17:04
Changes: 08/24/2023 14:10 (36), 08/24/2023 14:12 (14), 08/24/2023 14:13 (2), 09/16/2023 16:56 (2), 09/16/2023 17:04 (21)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.