# CVE-2013-0347: Information disclosure in n/a

> Local attackers can read sensitive information from the webfs log file due to insecure world-readable permissions.

- **Severity:** High 7.2 (`AV:L/AC:L/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:** 16 Nov 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-0347, GHSA-7cg3-r6gj-jmv7

## What is CVE-2013-0347?

CVE-2013-0347 is a high-severity vulnerability in n/a, published on 16 Nov 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Gentoo init script for webfs uses world-readable permissions for /var/log/webfsd.log, which allows local users to have unspecified impact by reading the file.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2013-0347?

It affects 1 product.


Products: Webfs Webfs.

## How do I fix CVE-2013-0347?

Apply the vendor's patch.

## Is CVE-2013-0347 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0833](https://insights.sbomify.com/CVE-2003-0833/): Memory corruption in n/a (high 7.5)
- [CVE-2003-0445](https://insights.sbomify.com/CVE-2003-0445/): Memory corruption in n/a (high 7.5)
- [CVE-2003-0832](https://insights.sbomify.com/CVE-2003-0832/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-0347 and fix it if it is affected.

What it is: CVE-2013-0347 is a high-severity vulnerability in n/a, published on 16 Nov 2014. 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-2013-0347 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-2013-0347/ (Markdown: https://insights.sbomify.com/CVE-2013-0347/index.md)
```

## Sources

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

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