Skip to content
Fencer Intel
medium 5.5

CVE-2013-1820 json

tuned before 2.x allows local users to kill running processes due to insecure permissions with tuned's ktune service.

published 7y ago modified 4mo ago also EUVD-2013-1839

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 31%
public exploits
0
none known

Summary

tuned before 2.x allows local users to kill running processes due to insecure permissions with tuned's ktune service.

Patch / fix

  • redhat tuned 2.0.2

Is CVE-2013-1820 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2013-1820 updated cvss 4.0

tuned: insecure permissions of pmqos-static.pid

  • Red Hat Enterprise Linux 6 tuned, tuned-utils
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.38% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 4.7 AV:L/AC:M/Au:N/C:N/I:N/A:C

Affected products

  • tuned tuned

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.