Skip to content
Fencer Intel
medium 5.5

CVE-2015-3243 json

rsyslog uses weak permissions for generating log files, which allows local users to obtain sensitive information by reading files in /var/l…

published 2017-07-25 9 y ago modified 2026-06-17 4 mo ago also EUVD-2015-3298

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

Summary

rsyslog uses weak permissions for generating log files, which allows local users to obtain sensitive information by reading files in /var/log/cron.

Patch / fix

  • rsyslog SLES for SAP 12 SP3, SLES 12 SP3, SLED 12 SP3 8.24.0-3.3.1
  • rsyslog SLE Module for Server Applications 15, SLE Module for Basesystem 15 8.33.1-3.3.1

suse advisories SUSE-SU-2018:2038-1SUSE-SU-2018:1937-1SUSE-SU-2018:1937-2

  • rsyslog openSUSE Tumbleweed 8.2106.0-1.2

opensuse advisories openSUSE-SU-2024:11309-1

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-2015-3243 updated cvss 2.1

rsyslog: some log files are created world-readable

  • Red Hat Enterprise Linux 7 rsyslog, rsyslog-relp, rsyslog-snmp, rsyslog-kafka, rsyslog-mysql, rsyslog-pgsql, +11 more Red Hat Storage 2 rsyslog
    affected: workaround, no fix available
  • Red Hat Enterprise Linux 5 rsyslog Red Hat Enterprise Linux 6 rsyslog, rsyslog-relp, rsyslog-snmp, rsyslog-mysql, rsyslog-pgsql, rsyslog-gnutls, +1 more
    not affected: vulnerable code not present

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.45% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Classification

Weakness
  • CWE-532 Insertion of Sensitive Information into Log File

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.