# CVE-2018-9310: Privilege escalation in n/a

> Local attackers can exploit a setuid root vulnerability in MagniComp SysInfo to gain root privileges and compromise the system.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 30 Apr 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-36vp-pvh3-w5x3

## What is CVE-2018-9310?

CVE-2018-9310 is a high-severity vulnerability in n/a, published on 30 Apr 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in MagniComp SysInfo before 10-H82 if setuid root (the default). This vulnerability allows any local user on a Linux/UNIX system to run SysInfo and obtain a root shell, which can be used to compromise the local system.

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

It affects 1 product.


Products: Magnicomp Sysinfo.

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

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

## Is CVE-2018-9310 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-6516](https://insights.sbomify.com/CVE-2017-6516/): Privilege escalation in n/a (medium 6.7)
- [CVE-2018-7268](https://insights.sbomify.com/CVE-2018-7268/): Information disclosure in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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