dbcve.org
InbodyApplication

CVE-2021-20832

MEDIUM · 5.3 CVSS v3.1 Published 2021-10-13
Fix available
A fix is available. Upgrade to 2.2.90 / 2.3.30 or later.
See remediation →
62/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
InBody App for iOS versions prior to 2.3.30 and InBody App for Android versions prior to 2.2.90(510) contain a vulnerability which may lead to information disclosure only when it works with the body composition analyzer InBody Dial. This may allow an attacker who can connect to the InBody Dial with InBody App may obtain a victim's measurement result measured by InBody Dial.

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 confidence

InBody mobile applications for iOS and Android contain an information disclosure vulnerability when interfacing with InBody Dial body composition analyzers. The flaw allows an attacker who can connect to the InBody Dial device via the InBody App to obtain measurement results from other users who have used the same device, indicating a lack of proper authentication or authorization controls in the device pairing/communication protocol.

MitigationUpdate InBody App for iOS to version 2.3.30 or later, and InBody App for Android to version 2.2.90(510) or later.

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
InbodyApplication
Affected:< 2.2.90< 2.3.30

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 if InBody mobile app is installed
    Check your iOS device (App Library or home screen) or Android device (app drawer or home screen) for the InBody app icon
    Affected if The InBody app is present on your device
  2. Check InBody app version on iOS
    Open the App Store, tap your profile icon, scroll to InBody app and check the version number, or go to Settings > General > iPhone Storage > InBody to view version
    Affected if iOS version is below 2.3.30
  3. Check InBody app version on Android
    Open Google Play Store, search for InBody app, tap to view details and check the version, or go to Settings > Apps > InBody to view version information
    Affected if Android version is below 2.2.90 (510)
  4. Determine if InBody Dial device pairing is used
    Open the InBody app and check if you have paired or connected to an InBody Dial body composition analyzer device
    Affected if You have paired with an InBody Dial device using the InBody app

You are affected if the InBody app is installed with a version below 2.3.30 on iOS or below 2.2.90 on Android AND you have connected the app to an InBody Dial device, as this creates the condition where other users measurement data could be accessed without authorization.

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.

dbcve · scoped
Upgrade available Upgrade to 2.2.90 / 2.3.30 or later
Fixed in 2.2.902.3.30
Interim mitigation

Update InBody App for iOS to version 2.3.30 or later, and InBody App for Android to version 2.2.90(510) or later.

Recommended fix High confidence

InBody App for iOS to version 2.3.30 or later; InBody App for Android to version 2.2.90(510) or later

  1. For iOS: Open the App Store, search for 'InBody App', and update to version 2.3.30 or later
  2. For Android: Open Google Play Store, search for 'InBody App', and update to version 2.2.90(510) or later
  3. Alternatively, uninstall the existing InBody App and reinstall from the app store to ensure the latest version is obtained
  4. After updating, verify the installed version in the app settings to confirm the fix is applied

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Inbody Scoped from the published advisory
  • Consultation1.0 h
  • Implementation0.5 h
  • Testing1.0 h
  • Review / QA0.5 h
3.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-20832 — 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-20832 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