C 230 Firmware
Approved changes feed: RSS · Atom
cpe:2.3:o:arista:c-230_firmware:*:*:*:*:*:*:*:*
part: o version: * update: *
| Vendor | Arista (6527c28e-420f-5910-9f50-47683159f01a) |
|---|---|
| Product | C 230 Firmware (90c093d0-4bab-5108-8bcd-54a0d4a8c9cc) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2020-26146 |
vulnerable | 2026-06-08 05:23:50.696619 |
Details available
An issue was discovered on Samsung Galaxy S3 i9305 4.4.4 devices. The WPA, WPA2, and WPA3 implementations reassemble fragments with non-consecutive packet numbers. An adversary can abuse this to exfiltrate selected fragments. This vulnerability is exploitable when another device sends fragmented frames and the WEP, CCMP, or GCMP data-confidentiality protocol is used. Note that WEP is vulnerable to this attack by design.
Published: 2021-05-11T19:39:07.000Z
Updated: 2026-06-02T13:53:46.824Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-26144 |
vulnerable | 2026-06-08 05:23:50.646027 |
Details available
An issue was discovered on Samsung Galaxy S3 i9305 4.4.4 devices. The WEP, WPA, WPA2, and WPA3 implementations accept plaintext A-MSDU frames as long as the first 8 bytes correspond to a valid RFC1042 (i.e., LLC/SNAP) header for EAPOL. An adversary can abuse this to inject arbitrary network packets independent of the network configuration.
Published: 2021-05-11T19:33:04.000Z
Updated: 2026-04-14T08:49:08.532Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-24586 |
vulnerable | 2026-06-08 05:22:34.473744 |
Details available
The 802.11 standard that underpins Wi-Fi Protected Access (WPA, WPA2, and WPA3) and Wired Equivalent Privacy (WEP) doesn't require that received fragments be cleared from memory after (re)connecting to a network. Under the right circumstances, when another device sends fragmented frames encrypted using WEP, CCMP, or GCMP, this can be abused to inject arbitrary network packets and/or exfiltrate user data.
Published: 2021-05-11T00:00:00.000Z
Updated: 2024-08-04T15:19:08.804Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.