# CVE-2011-0343: Misconfiguration in n/a

> Local attackers can read and modify log files due to insecure permissions caused by improper cast operations in syslog-ng on FreeBSD or HP-UX.

- **Severity:** Medium 6.9 (`AV:L/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** 28 Jan 2011
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2011-0343, GHSA-mw34-97q8-x4qh

## What is CVE-2011-0343?

CVE-2011-0343 is a medium-severity vulnerability in n/a, published on 28 Jan 2011. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Balabit syslog-ng 2.0, 3.0, 3.1, 3.2 OSE and PE, when running on FreeBSD or HP-UX, does not properly perform cast operations, which causes syslog-ng to use a default value of -1 to create log files with insecure permissions (07777), which allows local users to read and write to these log files.

Weakness: CWE-264

## Which versions are affected by CVE-2011-0343?

It affects 1 product.


Products: Oneidentity Syslog-Ng.

## How do I fix CVE-2011-0343?

Upgrade to a fixed version.

## Is CVE-2011-0343 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-5110](https://insights.sbomify.com/CVE-2008-5110/): Other in n/a (critical 9.3)
- [CVE-2020-8019](https://insights.sbomify.com/CVE-2020-8019/): syslog-ng: Local privilege escalation from new to root in %post (high 7.7)
- [CVE-2022-38725](https://insights.sbomify.com/CVE-2022-38725/): Integer overflow in n/a (high 7.5)
- [CVE-2002-1200](https://insights.sbomify.com/CVE-2002-1200/): Memory corruption in n/a (high 7.5)
- [CVE-2011-1951](https://insights.sbomify.com/CVE-2011-1951/): Denial of service in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-0343 and fix it if it is affected.

What it is: CVE-2011-0343 is a medium-severity vulnerability in n/a, published on 28 Jan 2011. 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-2011-0343 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-2011-0343/ (Markdown: https://insights.sbomify.com/CVE-2011-0343/index.md)
```

## Sources

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

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