dbcve.org
LogiopsApplication · Pixlone

CVE-2024-45752

HIGH · 7.3 CVSS v3.1 Published 2024-09-19
Fix available
A fix is available. Upgrade to after 0.3.4 or later.
See remediation →
76/100
Remediation priority · High
No privileges

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

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

logiops through 0.3.4 ships with a default configuration that exposes the logid daemon via an unrestricted D-Bus service, permitting any unprivileged local user to reconfigure the daemon including injecting malicious keyboard macros. This allows local privilege escalation with minimal user interaction.

MitigationRestrict the D-Bus service configuration to require authenticated/authorized access, limiting which users or groups can invoke logid configuration methods, or disable the exposed D-Bus interface if not required.

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
LogiopsApplication
Affected:<= 0.3.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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L

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. Check if logiops/logid daemon is installed
    Run 'which logid' or look for the logid binary in common paths like /usr/bin/logid, /usr/sbin/logid. Also check package managers: dpkg -l | grep logiops, rpm -qa | grep logiops, or pacman -Q logiops
    Affected if The logid binary is found on the system
  2. Determine the installed logiops version
    Run 'logid --version' or 'logid -v' if available. If not, check the package version via your system package manager
    Affected if The version is 0.3.4 or lower (any version up to and including 0.3.4)
  3. Locate the D-Bus service configuration for logid
    Look for D-Bus service files in /usr/share/dbus-1/system-services/ or /usr/share/dbus-1/services/ directory. Search for files containing 'logiops' or 'logid' in the filename, for example: find /usr/share/dbus-1 -name '*logi*' -o -name '*logid*'
    Affected if A D-Bus service file for logid exists in these directories
  4. Inspect the D-Bus service file for access restrictions
    Read the found D-Bus service file (typically in XML format). Check if it contains <allow> elements without 'user' or 'group' constraints, or lacks <policy> restrictions. Specifically look for lines like '<allow send_destination="org.pixl.logiops"/>' with no user/group restrictions
    Affected if The D-Bus service file allows any user to send messages to the service without authentication or authorization constraints
  5. Check if D-Bus interface is enabled in logid configuration
    Examine the logid configuration file - typically found at ~/.config/logid.cfg, /etc/logid.cfg, or /etc/logiops.cfg. Look for a 'dbus' or 'dbus_enable' setting. If present, check if it is set to true or enabled
    Affected if D-Bus interface is explicitly enabled in the configuration file

The system is affected if logiops version 0.3.4 or lower is installed with the D-Bus service exposed to any unprivileged local user (no authentication/authorization policy in the D-Bus service file).

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 a release after 0.3.4
Interim mitigation

Restrict the D-Bus service configuration to require authenticated/authorized access, limiting which users or groups can invoke logid configuration methods, or disable the exposed D-Bus interface if not required.

Recommended fix Moderate confidence

A version newer than 0.3.4 (check GitHub releases for the specific fixed version)

  1. 1. Check the current installed version of logiops: `logid --version` or check your package manager
  2. 2. If using a package manager (apt, yum, dnf, pacman, etc.), update to the latest available package
  3. 3. If building from source, clone the repository and check for version tags: `git tag | sort -V`
  4. 4. Build and install the latest version following the project's build instructions
  5. 5. Verify the D-Bus configuration file (/etc/dbus-1/system.d/logid.conf or similar) restricts access appropriately
  6. 6. Restart the logid service: `sudo systemctl restart logid` or `sudo systemctl restart logiops`
  7. 7. Confirm the service is running correctly: `systemctl status logid`
Caveat Review release notes for any configuration file changes that may require manual migration

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

Fix this in Logiops Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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