# CVE-2018-7268: Information disclosure in n/a

> A local unprivileged user can read any root-owned file, exposing sensitive data like password hashes and private keys in BMC BladeLogic Automation.

- **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:** No
- **Published:** 21 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v5vm-78qg-9j5r

## What is CVE-2018-7268?

CVE-2018-7268 is a medium-severity vulnerability in n/a, published on 21 May 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

MagniComp SysInfo before 10-H81, as shipped with BMC BladeLogic Automation and other products, contains an information exposure vulnerability in which a local unprivileged user is able to read any root (uid 0) owned file on the system, regardless of the file permissions. Confidential information such as password hashes (/etc/shadow) or other secrets (such as log files or private keys) can be leaked to the attacker. The vulnerability has a confidentiality impact, but has no direct impact on system integrity or availability.

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

## Which versions are affected by CVE-2018-7268?

It affects 1 product.


Products: Magnicomp Sysinfo.

## How do I fix CVE-2018-7268?

No fix has been published for CVE-2018-7268 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-7268 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-9310](https://insights.sbomify.com/CVE-2018-9310/): Privilege escalation in n/a (high 7.8)
- [CVE-2017-6516](https://insights.sbomify.com/CVE-2017-6516/): Privilege escalation in n/a (medium 6.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-7268 and fix it if it is affected.

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

## Sources

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

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