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

> Local attackers can read sensitive SNMP community strings from the configuration file due to insecure file permissions.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/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:** 10 Nov 2015
- **Updated:** 6 Aug 2024
- **Also known as:** ALPINE-CVE-2015-8100, GHSA-88wg-39x8-pwf8

## What is CVE-2015-8100?

CVE-2015-8100 is a low-severity vulnerability in n/a, published on 10 Nov 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The net-snmp package in OpenBSD through 5.8 uses 0644 permissions for snmpd.conf, which allows local users to obtain sensitive community information by reading this file.

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

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

It affects 1 product.


Products: Net-Snmp Net-Snmp.

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

Apply the vendor's patch.

## Is CVE-2015-8100 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-4837](https://insights.sbomify.com/CVE-2005-4837/): Use after free in n/a (critical 10.0)
- [CVE-2005-1740](https://insights.sbomify.com/CVE-2005-1740/): Path traversal in n/a (critical 10.0)
- [CVE-2007-5846](https://insights.sbomify.com/CVE-2007-5846/): Denial of service in n/a (high 7.8)
- [CVE-2018-18066](https://insights.sbomify.com/CVE-2018-18066/): Null dereference in n/a (high 7.5)
- [CVE-2015-5621](https://insights.sbomify.com/CVE-2015-5621/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-8100 is a low-severity vulnerability in n/a, published on 10 Nov 2015. 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-8100 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-8100/ (Markdown: https://insights.sbomify.com/CVE-2015-8100/index.md)
```

## Sources

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

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