# CVE-2022-41769: Privilege escalation in Intel(R) Connect M Android application

> An authenticated local user can escalate privileges in the Intel Connect M Android application due to improper access control.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 May 2023
- **Updated:** 24 Jan 2025
- **Also known as:** GHSA-36h7-836c-vp8g

## What is CVE-2022-41769?

CVE-2022-41769 is a medium-severity vulnerability in Intel(R) Connect M Android application, published on 10 May 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Improper access control in the Intel(R) Connect M Android application before version 1.82 may allow an authenticated user to potentially enable escalation of privilege via local access.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2022-41769?

It affects 1 product.


Products: Intel Connect M.

## How do I fix CVE-2022-41769?

No fix has been published for CVE-2022-41769 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-41769 being exploited?

There is no known exploitation of CVE-2022-41769 in the wild and no public exploit code.

## Other vulnerabilities in Intel(R) Connect M Android application

- [CVE-2021-44470](https://insights.sbomify.com/CVE-2021-44470/): Information disclosure in Intel(R) Connect M Android application (medium 5.5)
- [CVE-2022-41801](https://insights.sbomify.com/CVE-2022-41801/): Denial of service in Intel(R) Connect M Android application (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41769 and fix it if it is affected.

What it is: CVE-2022-41769 is a medium-severity vulnerability in Intel(R) Connect M Android application, published on 10 May 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-41769 in the wild and no public exploit code.

Affected product: Intel(R) Connect M Android application. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-41769/ (Markdown: https://insights.sbomify.com/CVE-2022-41769/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-41769
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-41769
- OSV: https://osv.dev/vulnerability/CVE-2022-41769

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-41769/
Summaries are generated and may contain mistakes; the official description above is the record.