# CVE-2015-3243: Information disclosure in n/a

> Local users can read sensitive log files due to weak permissions, exposing information to unauthorized local attackers.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jul 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-3243, ECHO-d0db-1a35-e8b6, GHSA-mg7r-rgfr-mmj9, SUSE-SU-2018:1937-1, SUSE-SU-2018:1937-2, SUSE-SU-2018:2038-1, openSUSE-SU-2024:11309-1

## What is CVE-2015-3243?

CVE-2015-3243 is a medium-severity vulnerability in n/a, published on 25 Jul 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2015-3243?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rsyslog` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 8.24.0-3.3.1 |
| `rsyslog` | SUSE:Linux Enterprise Module for Basesystem 15 | All versions | 8.33.1-3.3.1 |
| `rsyslog` | SUSE:Linux Enterprise Module for Basesystem 15 | All versions | 8.33.1-3.3.1 |
| `rsyslog` | SUSE:Linux Enterprise Module for Server Applications 15 | All versions | 8.33.1-3.3.1 |
| `rsyslog` | SUSE:Linux Enterprise Module for Server Applications 15 | All versions | 8.33.1-3.3.1 |
| `rsyslog` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 8.24.0-3.3.1 |
| `rsyslog` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 8.24.0-3.3.1 |
| `rsyslog` | openSUSE:Tumbleweed | All versions | 8.2106.0-1.2 |

Products: Rsyslog Rsyslog.

## How do I fix CVE-2015-3243?

Apply the vendor's patch.

## Is CVE-2015-3243 being exploited?

There is no known exploitation of CVE-2015-3243 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2019-17040](https://insights.sbomify.com/CVE-2019-17040/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-12588](https://insights.sbomify.com/CVE-2017-12588/): Other in n/a (critical 9.8)
- [CVE-2008-5617](https://insights.sbomify.com/CVE-2008-5617/): Auth bypass in n/a (high 8.5)
- [CVE-2014-3634](https://insights.sbomify.com/CVE-2014-3634/): Memory corruption in n/a (high 7.5)
- [CVE-2013-4758](https://insights.sbomify.com/CVE-2013-4758/): Use after free in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-3243 and fix it if it is affected.

What it is: CVE-2015-3243 is a medium-severity vulnerability in n/a, published on 25 Jul 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-3243 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-3243/ (Markdown: https://insights.sbomify.com/CVE-2015-3243/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-3243
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-3243
- OSV: https://osv.dev/vulnerability/CVE-2015-3243

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-3243/
Summaries are generated and may contain mistakes; the official description above is the record.