Samsung Galaxy i9305 Firmware 4.4.4
Approved changes feed: RSS · Atom
cpe:2.3:o:samsung:galaxy_i9305_firmware:4.4.4:*:*:*:*:*:*:*
part: o version: 4.4.4 update: *
| Vendor | Samsung (0eb241f7-997b-5d1c-b2a3-00a89e1049d3) |
|---|---|
| Product | Galaxy I9305 Firmware (14ba7553-e947-5ffd-9ff4-3ae90aad95e3) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
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.695885 |
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-26145 |
vulnerable | 2026-06-08 05:23:50.660807 |
Details available
An issue was discovered on Samsung Galaxy S3 i9305 4.4.4 devices. The WEP, WPA, WPA2, and WPA3 implementations accept second (or subsequent) broadcast fragments even when sent in plaintext and process them as full unfragmented frames. An adversary can abuse this to inject arbitrary network packets independent of the network configuration.
Published: 2021-05-11T19:35:10.000Z
Updated: 2026-04-14T08:49:09.886Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-26144 |
vulnerable | 2026-06-08 05:23:50.642554 |
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 |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.