# CVE-2024-45752: Privilege escalation in n/a

> Unprivileged users can configure the logid daemon via D-Bus to set malicious keyboard macros, leading to privilege escalation.

- **Severity:** High 8.5 (`CVSS:3.1/AC:L/AV:L/A:L/C:H/I:H/PR:N/S:C/UI:R`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 19 Sep 2024
- **Updated:** 20 Sep 2024
- **Also known as:** DEBIAN-CVE-2024-45752, GHSA-6ffr-69v4-q8xm, UBUNTU-CVE-2024-45752

## What is CVE-2024-45752?

CVE-2024-45752 is a high-severity vulnerability in n/a, published on 19 Sep 2024. 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

logiops through 0.3.4, in its default configuration, allows any unprivileged user to configure its logid daemon via an unrestricted D-Bus service, including setting malicious keyboard macros. This allows for privilege escalation with minimal user interaction.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2024-45752?

It affects 1 product.


Products: Pixlone Logiops.

## How do I fix CVE-2024-45752?

Upgrade to a fixed version.

## Is CVE-2024-45752 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-45752 and fix it if it is affected.

What it is: CVE-2024-45752 is a high-severity vulnerability in n/a, published on 19 Sep 2024. 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-2024-45752 in the wild and no public exploit code.

Affected product: n/a. 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-2024-45752/ (Markdown: https://insights.sbomify.com/CVE-2024-45752/index.md)
```

## Sources

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

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