CVE-2024-52336
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 · uneditedA script injection vulnerability was identified in the Tuned package. The `instance_create()` D-Bus function can be called by locally logged-in users without authentication. This flaw allows a local non-privileged user to execute a D-Bus call with `script_pre` or `script_post` options that permit arbitrary scripts with their absolute paths to be passed. These user or attacker-controlled executable scripts or programs could then be executed by Tuned with root privileges that could allow attackers to local privilege escalation.
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 confidenceA script injection vulnerability in the Tuned system tuning daemon allows local privilege escalation. The D-Bus method instance_create() lacks authentication, enabling any locally logged-in user to invoke it with script_pre or script_post parameters containing absolute paths to arbitrary executables. Since Tuned runs with root privileges, attacker-controlled scripts execute with elevated privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Tuned daemon is runningRun 'systemctl status tuned' or check for tuned process with 'ps aux | grep tuned'Affected if Tuned daemon is active and running with root privileges
-
Identify installed Tuned versionRun 'tuned --version' or 'rpm -q tuned' (RHEL) / 'dpkg -l tuned' (Debian) to get the package versionAffected if Version is lower than the patched version (vendor-advisory referenced fix adds authentication to instance_create)
-
Check D-Bus policy for Tuned serviceInspect D-Bus configuration in /etc/dbus-1/system.d/ or run 'busctl call org.freedesktop.tuned1 /org/freedesktop/tuned1 org.freedesktop.tuned1 InstanceCreator InstanceCreate ss <param1> <param2>' as unprivileged userAffected if Unprivileged user can invoke instance_create method without authentication failure
-
Confirm script_pre/script_post parameters are acceptedTest calling instance_create with script_pre or script_post parameters containing an absolute path (e.g., /tmp/test) as a non-root user via D-BusAffected if Method accepts script_pre or script_post parameters from unprivileged user without authorization error
User is affected if Tuned daemon is running and unprivileged/local users can invoke the instance_create D-Bus method with script parameters without authentication.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply the vendor patch to Tuned that adds proper authentication and authorization to the instance_create() D-Bus method, restricting access to privileged users only.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52336 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-52336 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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