dbcve.org
Connect MApplication · Intel

CVE-2022-41801

MEDIUM · 5.5 CVSS v3.1 Published 2023-05-10
Fix available
A fix is available. Upgrade to 1.82 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
Uncontrolled resource consumption in the Intel(R) Connect M Android application before version 1.82 may allow an authenticated user to potentially enable denial of service 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 · moderate confidence

The Intel Connect M Android application before version 1.82 contains an uncontrolled resource consumption vulnerability. An authenticated user with local access can exploit this to cause denial of service by exhausting system resources.

MitigationUpdate Intel Connect M Android application to version 1.82 or later to remediate this vulnerability.

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.82

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

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

  1. Locate Intel Connect M on the Android device
    Open Settings > Apps and search for 'Intel Connect M', or locate the app icon in the application drawer
    Affected if The app is present on the device and can be located in the app list
  2. Check the installed version number
    In Settings > Apps > Intel Connect M, read the Version info displayed under the app name
    Affected if The version shown is a number less than 1.82 (for example, 1.80, 1.75, 1.60)
  3. Verify version through APK if the file is available
    Use an APK inspector or extraction tool to read the versionName attribute from the Intel Connect M APK manifest
    Affected if The versionName attribute in the APK is less than 1.82

The environment is affected if Intel Connect M Android application is installed with a version lower than 1.82

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.82 or later
Fixed in 1.82
Interim mitigation

Update Intel Connect M Android application to version 1.82 or later to remediate this vulnerability.

Recommended fix High confidence

1.82

  1. Open the Google Play Store on the Android device
  2. Search for 'Intel Connect M' or 'Connect M'
  3. Locate the Intel Connect M application in the search results
  4. Tap on the application to view its details
  5. Verify the version number displayed is 1.82 or later
  6. If an update is available, tap the 'Update' button
  7. Wait for the update to download and install completely
  8. Once installed, open the app and verify functionality

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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