CVE-2018-20100
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 August Connect devices. Insecure data transfer between the August app and August Connect during configuration allows attackers to discover home Wi-Fi credentials. This data transfer uses an unencrypted access point for these credentials, and passes them in an HTTP POST, using the AugustWifiDevice class, with data encrypted with a fixed key found obfuscated in the app.
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 · high confidenceDuring August Connect device configuration, Wi-Fi credentials are transmitted over an unencrypted access point in an HTTP POST request via the AugustWifiDevice class. The credentials are encrypted with a fixed key that is obfuscated within the app binary, allowing attackers to extract this key and decrypt captured traffic to obtain home Wi-Fi credentials.
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 dataall versionsall versionsCVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Identify August Connect devices in your environmentInventory your network for August Connect or August Smart Connect devices. Check device documentation, network scans, or DHCP logs for device hostname or MAC address patterns associated with August products.Affected if August Connect devices are present on the network
-
Monitor configuration traffic for HTTP usageDuring new device setup or factory reset, capture network traffic on the client device or network tap. Inspect the HTTP requests sent to the August configuration server - look for POST requests to endpoints that do not use HTTPS (port 80 instead of 443).Affected if HTTP POST requests are observed during device configuration instead of HTTPS
-
Verify Wi-Fi setup access point encryptionWhen configuring an August Connect, observe the temporary Wi-Fi network it creates for setup. Check if the access point is open/unencrypted (no WPA2/WPA3 password required) and if the subsequent credential submission travels over plain HTTP.Affected if Device configuration occurs over an unencrypted access point with credentials sent via unencrypted HTTP
-
Check for hardcoded encryption indicators in app trafficAnalyze captured configuration traffic for patterns indicating fixed-key encryption of Wi-Fi credentials. Compare traffic to known behavior where credentials are encrypted client-side before transmission rather than protected by TLS.Affected if Wi-Fi credentials appear encrypted with a static key in the payload rather than protected by TLS transport encryption
If you have August Connect devices and perform device configuration over their temporary unencrypted setup network with credentials sent via HTTP, you are affected by this 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 dataReplace the hardcoded/obfuscated encryption key with dynamically generated keys, enforce TLS encryption for all network communication during device configuration, and implement certificate pinning to prevent man-in-the-middle attacks.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-20100 — 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-2018-20100 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