CVE-2020-26144
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Samsung Galaxy S3 i9305 WiFi driver (WEP/WPA/WPA2/WPA3) incorrectly validates incoming A-MSDU frames, accepting plaintext frames when the first 8 bytes match a valid RFC1042 (LLC/SNAP) header for EAPOL. This allows an attacker within radio range to inject arbitrary network packets independently of the network's security configuration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 4.4.4< 10.0.1-31< 10.0.1-31< 10.0.1-31< 10.0.1-31< 11.0.0-36< 11.0.0-36< 11.0.0-36CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Samsung Galaxy S3 i9305 deviceCheck device model number in system settings under 'About phone' or use 'getprop ro.product.model' command in ADB shellAffected if Device model is exactly SM-I9305 or I9305 running Android 4.4.4
-
Verify Android version on Samsung deviceCheck Android version in Settings > About phone > Android version, or run 'getprop ro.build.version.release' in ADB shellAffected if Android version is exactly 4.4.4 (KitKat)
-
Identify Arista switch modelUse command 'show version' or check physical labeling on the switch chassis to identify the exact C-series model (C 250, C 260, C 230, C 235, C 200, C 120, or C 130)Affected if Switch is an Arista C 250, C 260, C 230, C 235, C 200, C 120, or C 130 model
-
Check Arista firmware version for C 250/260/230/235Run 'show version' command and note the EOS version displayedAffected if Firmware version is less than 10.0.1-31 on C 250, C 260, C 230, or C 235 models
-
Check Arista firmware version for C 200/120/130Run 'show version' command and note the EOS version displayedAffected if Firmware version is less than 11.0.0-36 on C 200, C 120, or C 130 models
You are affected if you have a Samsung Galaxy S3 I9305 on Android 4.4.4, or an Arista C-series switch (C 250/260/230/235 below 10.0.1-31, or C 200/120/130 below 11.0.0-36) using WiFi functionality.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data10.0.1-3111.0.0-36
This is a firmware-level vulnerability in an end-of-life device (Android 4.4.4). The primary mitigation is to avoid using this device on untrusted networks, implement network segmentation to isolate vulnerable clients, and ideally retire the device since no vendor patch is expected.
- Consultation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26144 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-26144 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data