Skip to main content
No exploitation reportedFix available

CVE-2015-3243

No exploitation reported by the sources we read.

  • Published2017-07-25
  • WeaknessCWE-532

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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

Timeline

dates in UTC
  1. 2017-07-2518:29CVE publishedNVD

Versions per branch

NVD
Rsyslog
BranchAffectedFixed in
—all versionsno fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • rsyslogWolfiall versions · no fixed version listedand 35 other packages
  • rsyslogSUSE:Linux Enterprise Server for SAP Applications 12 SP3all versions · fixed in 8.24.0-3.3.1
  • rsyslogSUSE:Linux Enterprise Server 12 SP3all versions · fixed in 8.24.0-3.3.1
  • rsyslogSUSE:Linux Enterprise Module for Server Applications 15all versions · fixed in 8.33.1-3.3.1
  • rsyslogSUSE:Linux Enterprise Module for Basesystem 15all versions · fixed in 8.33.1-3.3.1
  • rsyslogSUSE:Linux Enterprise Desktop 12 SP3all versions · fixed in 8.24.0-3.3.1
  • rsyslogopenSUSE:Tumbleweedall versions · fixed in 8.2106.0-1.2
  • rsyslogEchoall versions · no fixed version listed

4 more package ranges on OSV.dev

Vendor advisories

  • CVE-2015-3243 Red Hat Product Security20 known affected

    rsyslog: some log files are created world-readable

    rsyslog as a component of Red Hat Enterprise Linux 7 · rsyslog-crypto as a component of Red Hat Enterprise Linux 7 · rsyslog-doc as a component of Red Hat Enterprise Linux 7 · +17 more

Full record on NVD

Fix

  1. Workaround from the vendor Red Hat Product Security CVE-2015-3243 · 20 productsPlease add: create 0600 root root to the /etc/logrotate.d/syslog file, this will ensure the file is created with permissions when logrotate runs. It is also recommended that users manually set the permissions on existing or newly installed log files in order to prevent access by untrusted users.
  2. No fix available, says the vendor Red Hat Product Security CVE-2015-3243 · 20 productsAffected

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Published
2017-07-25
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-mg7r-rgfr-mmj9

Frequently asked questions

What is CVE-2015-3243?

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

Is CVE-2015-3243 actively exploited?

Active exploitation of CVE-2015-3243 has not been confirmed. Its EPSS score was 0.4% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2015-3243?

CVE-2015-3243 has a CVSS v3 base score of 5.5 (MEDIUM severity), with vector string CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.

Running rsyslog? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record