dbcve.org
Connect MApplication · Intel

CVE-2021-44470

MEDIUM · 5.5 CVSS v3.1 Published 2022-08-18
Fix available
A fix is available. Upgrade to 1.7.4 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Incorrect default permissions for the Intel(R) Connect M Android application before version 1.7.4 may allow an authenticated user to potentially enable information disclosure via local access.

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 Intel Connect M Android application before version 1.7.4 has incorrect default file permissions that allow an authenticated local user to access sensitive information that should be protected. This is a classic Android permission misconfiguration where the app stores data with overly permissive access rights, enabling other local users or potentially other apps to read confidential data.

MitigationUpdate the Intel Connect M Android application to version 1.7.4 or later. Additionally, review and correct all default file and data storage permissions to ensure sensitive information is not accessible to unauthorized users or applications.

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
Connect MApplication
Affected:< 1.7.4

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Verify Intel Connect M is installed
    Run 'pm list packages | grep -i connect' on the Android device to list installed packages containing 'connect', or check app drawer for Intel Connect M icon
    Affected if The package com.intel.connectm or similar Intel Connect M package is found on the device
  2. Determine installed version
    Run 'dumpsys package [package_name]' to retrieve version info, or check app details in Settings > Apps > Intel Connect M > Version
    Affected if The displayed version number is lower than 1.7.4 (e.g., 1.7.3, 1.6.x, etc.)
  3. Check app data directory permissions
    Use a root-enabled shell or ADB to run 'ls -la /data/data/[package_name]/' and examine the permission bits on directories like shared_prefs, databases, or files
    Affected if Any directory or file shows permissions like 'rwxrwxrwx' (777) or 'rwxrwxrwx' (775) instead of 'rwx------' (700) or similar restrictive owner-only access
  4. Inspect shared preferences file permissions
    Run 'ls -la /data/data/[package_name]/shared_prefs/' to list XML preference files
    Affected if Files are readable by other users or apps (permissions include 'r--r--r--' or 'r--r--r--' allowing world/group read)
  5. Check database file permissions
    Run 'ls -la /data/data/[package_name]/databases/' to list SQLite database files
    Affected if Database files are readable by other users or apps, showing permissions that allow access beyond the app's own uid

If Intel Connect M version is below 1.7.4 AND sensitive app data directories or files have overly permissive permissions (world-readable or group-readable), the environment is affected by this vulnerability.

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 1.7.4 or later
Fixed in 1.7.4
Interim mitigation

Update the Intel Connect M Android application to version 1.7.4 or later. Additionally, review and correct all default file and data storage permissions to ensure sensitive information is not accessible to unauthorized users or applications.

Recommended fix High confidence

Intel Connect M version 1.7.4

  1. Upgrade the Intel(R) Connect M Android application to version 1.7.4 or later from the official Intel source or Google Play Store

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

Fix this in Connect M Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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