dbcve.org
TunedApplication · Redhat

CVE-2013-1820

MEDIUM · 5.5 CVSS v3.1 Published 2019-11-08
Fix available
A fix is available. Upgrade to 2.0.2 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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
tuned before 2.x allows local users to kill running processes due to insecure permissions with tuned's ktune service.

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 · moderate confidence

The tuned daemon (versions before 2.x) includes a ktune service component with insecure permissions that allows local unprivileged users to terminate arbitrary running processes on the system.

MitigationUpgrade tuned to version 2.x or later to resolve the permission vulnerability, or manually restrict permissions on the ktune service to prevent unauthorized process termination.

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
TunedApplication
Affected:< 2.0.2
FedoraOperating system
Affected:= 17

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if tuned or ktune package is installed
    Run 'rpm -qa | grep -i tuned' or 'rpm -qa | grep -i ktune' to list installed packages
    Affected if No tuned or ktune packages are found - the system is not affected because the vulnerable software is not installed
  2. Determine installed tuned version
    Run 'rpm -q --qf '%{VERSION}\n' tuned' to get the version number
    Affected if Version is less than 2.0.2 (for Red Hat) or the package is present on Fedora 17 - the system falls within affected version ranges
  3. Check if ktune service exists
    Run 'systemctl list-units --type=service | grep ktune' or 'ls /etc/init.d/ktune' to locate the ktune service
    Affected if The ktune service is present - the vulnerable component is available and could be exploited
  4. Inspect ktune service permissions and ownership
    Run 'ls -la /etc/init.d/ktune' (SysVinit) or check ktune.service unit file permissions with 'systemctl cat ktune'
    Affected if The ktune service file or binary is world-writable or accessible by unprivileged users - the insecure permission condition exists

A system is affected if tuned version is below 2.0.2 on Red Hat or running on Fedora 17, and the ktune service component with insecure permissions is present and accessible to unprivileged users.

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.

From vendor data
Upgrade available Upgrade to 2.0.2 or later
Fixed in 2.0.2
Interim mitigation

Upgrade tuned to version 2.x or later to resolve the permission vulnerability, or manually restrict permissions on the ktune service to prevent unauthorized process termination.

Fix this in Tuned Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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