# CVE-2017-5198: SolarWinds LEM (aka SIEM) before 6.3.1 has an incorrect sudo configuration, which allows local users to obtain root access by editing /usr/l


- **Severity:** High 8.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h648-2gvx-q57p

## What is CVE-2017-5198?

CVE-2017-5198 is a high-severity vulnerability in n/a, published on 24 Mar 2017. 

### Official description

SolarWinds LEM (aka SIEM) before 6.3.1 has an incorrect sudo configuration, which allows local users to obtain root access by editing /usr/local/contego/scripts/hostname.sh.

## Which versions are affected by CVE-2017-5198?

It affects 1 product.


Products: Solarwinds Log and Event Manager.

## How do I fix CVE-2017-5198?

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

## Is CVE-2017-5198 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-5199](https://insights.sbomify.com/CVE-2017-5199/): Code injection in n/a (high 8.8)
- [CVE-2015-7839](https://insights.sbomify.com/CVE-2015-7839/): Command injection in n/a (high 7.5)
- [CVE-2015-7840](https://insights.sbomify.com/CVE-2015-7840/): Command injection in n/a (high 7.5)
- [CVE-2014-5504](https://insights.sbomify.com/CVE-2014-5504/): Hardcoded credentials in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-5198 and fix it if it is affected.

What it is: CVE-2017-5198 is a high-severity vulnerability in n/a, published on 24 Mar 2017. 
Exploitation: There is no known exploitation of CVE-2017-5198 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-2017-5198/ (Markdown: https://insights.sbomify.com/CVE-2017-5198/index.md)
```

## Sources

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

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