# CVE-2023-41775: Missing authorization in 'direct' Desktop App for macOS

> A local attacker can bypass access restrictions to use the camera and microphone without user consent in the direct Desktop App for macOS.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2023
- **Updated:** 26 Sep 2024
- **Also known as:** GHSA-xcc9-j34m-89fm

## What is CVE-2023-41775?

CVE-2023-41775 is a medium-severity missing authorization vulnerability in L is B Corp. 'direct' Desktop App for macOS, published on 8 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper access control vulnerability in 'direct' Desktop App for macOS ver 2.6.0 and earlier allows a local attacker to bypass access restriction and to use camrea, microphone, etc. of the device where the product is installed without the user's consent.

## Which versions are affected by CVE-2023-41775?

It affects 1 product.


Products: L-Is-B Direct.

## How do I fix CVE-2023-41775?

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

## Is CVE-2023-41775 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-41775 and fix it if it is affected.

What it is: CVE-2023-41775 is a medium-severity missing authorization vulnerability in L is B Corp. 'direct' Desktop App for macOS, published on 8 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-41775 in the wild and no public exploit code.

Affected product: L is B Corp. 'direct' Desktop App for macOS. 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-2023-41775/ (Markdown: https://insights.sbomify.com/CVE-2023-41775/index.md)
```

## Sources

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

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