CVE-2019-20612
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 mobile devices with N(7.x) and O(8.x) (Broadcom Wi-Fi, and SEC Wi-Fi chipsets) software. Wi-Fi allows a denial of service via TCP SYN packets. The Samsung ID is SVE-2018-13162 (March 2019).
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 confidenceA denial of service vulnerability in the Wi-Fi stack of Samsung mobile devices running Android N (7.x) and O (8.x) allows attackers to crash or hang Wi-Fi functionality by sending specially crafted TCP SYN packets. The issue affects devices with Broadcom and SEC Wi-Fi chipsets.
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= 7.0= 7.1.0= 7.1.1= 7.1.2= 8.0= 8.1CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
-
Check Android OS versionGo to Settings > About Phone > Software Information > Android version. Alternatively, run 'getprop ro.build.version.release' via ADB shell.Affected if Android version is 7.0, 7.1.0, 7.1.1, 7.1.2, 8.0, or 8.1
-
Confirm device manufacturerCheck that the device is a Samsung model. Go to Settings > About Phone > Device name or manufacturer. Alternatively, run 'getprop ro.product.manufacturer' via ADB shell.Affected if Device is manufactured by Samsung
-
Verify Wi-Fi is enabledCheck that Wi-Fi is turned on. Go to Settings > Wi-Fi and ensure the toggle is enabled, or run 'cmd wifi status' via ADB shell.Affected if Wi-Fi functionality is active and capable of receiving network traffic
-
Check Wi-Fi chipset vendor (optional)This may require reviewing device specifications or using diagnostic tools. The affected chipsets are Broadcom and SEC (Samsung Electronics Co). Not all Samsung devices use these chipsets.Affected if Device uses a Broadcom or SEC Wi-Fi chipset
A Samsung device running Android 7.0-7.1.2 or Android 8.0-8.1 with an affected Broadcom or SEC Wi-Fi chipset and Wi-Fi enabled is potentially affected by this denial of service vulnerability.
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 dataApply Samsung's March 2019 security update (SVE-2018-13162) or upgrade to a later Android version that includes the patch. Users should avoid connecting to untrusted Wi-Fi networks as a precautionary measure.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20612 — 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-2019-20612 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