dbcve.org
Smart LifeApplication · Atomtech

CVE-2021-20732

MEDIUM · 5.9 CVSS v3.1 Published 2021-06-09
Fix available
A fix is available. Upgrade to 1.8.1 / 1.8.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The ATOM (ATOM - Smart life App for Android versions prior to 1.8.1 and ATOM - Smart life App for iOS versions prior to 1.8.2) does not verify server certificate properly, which allows man-in-the-middle attackers to eavesdrop on encrypted communication via a crafted certificate.

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 confidence

The ATOM Smart Life app for Android (versions prior to 1.8.1) and iOS (versions prior to 1.8.2) fails to properly validate server SSL/TLS certificates during encrypted communications. This certificate validation failure allows man-in-the-middle attackers to intercept and eavesdrop on traffic by presenting a crafted malicious certificate, effectively bypassing the protection provided by HTTPS encryption.

MitigationUpdate the ATOM Smart Life app to version 1.8.1 or later for Android, and version 1.8.2 or later for iOS, which implement proper server certificate validation.

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
Smart LifeApplication
Affected:< 1.8.1< 1.8.2

CVSS 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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the platform where the ATOM Smart Life app is installed
    Determine if the app is installed on Android or iOS. On Android, check the version in Settings > Apps > ATOM Smart Life. On iOS, check the version in the App Store app or in Settings > General > iPhone Storage > ATOM Smart Life.
    Affected if The app is installed on either platform and the version cannot be verified or is below the fixed release.
  2. Check the installed Android app version
    Navigate to Settings > Apps > ATOM Smart Life (or Apps & notifications > See all apps > ATOM Smart Life) and note the version number displayed. Alternatively, use ADB: adb shell dumpsys package com.atomtech.smartlife | grep versionName
    Affected if The displayed version is lower than 1.8.1.
  3. Check the installed iOS app version
    Open the App Store, search for ATOM Smart Life, and note the version number in the app listing. Or go to Settings > General > iPhone Storage, find ATOM Smart Life, and view the version info.
    Affected if The displayed version is lower than 1.8.2.
  4. Verify SSL certificate validation behavior (if version is confirmed)
    Since this is a client-side certificate validation flaw, there is no local configuration to inspect. The vulnerability exists in how the app validates certificates during HTTPS connections. If the version cannot be determined or confirmed as affected, treat the app as potentially vulnerable.
    Affected if The installed version is confirmed below 1.8.1 (Android) or below 1.8.2 (iOS).

A user is affected if the ATOM Smart Life app is running on Android with version below 1.8.1 or on iOS with version below 1.8.2, as these versions fail to properly validate SSL/TLS certificates and are susceptible to man-in-the-middle attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 1.8.1 / 1.8.2 or later
Fixed in 1.8.11.8.2
Interim mitigation

Update the ATOM Smart Life app to version 1.8.1 or later for Android, and version 1.8.2 or later for iOS, which implement proper server certificate validation.

Fix this in Smart Life Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-20732 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-20732 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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