# CVE-2015-8671: Privilege escalation in LogCenter V100R001C10

> An authenticated attacker can tamper with requests to escalate privileges and affect system functions in Huawei LogCenter.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9q6g-92h4-3m45

## What is CVE-2015-8671?

CVE-2015-8671 is a high-severity vulnerability in LogCenter V100R001C10, published on 2 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Huawei LogCenter V100R001C10 could allow an authenticated attacker to tamper with requests using a tool and submit a request to the server for privilege escalation, affecting some system functions.

Weakness: CWE-264

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

It affects 1 product.


Products: Huawei Logcenter.

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

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

## Is CVE-2015-8671 being exploited?

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

## Other vulnerabilities in LogCenter V100R001C10

- [CVE-2015-8670](https://insights.sbomify.com/CVE-2015-8670/): Denial of service in LogCenter V100R001C10 (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-8671 is a high-severity vulnerability in LogCenter V100R001C10, published on 2 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-8671 in the wild and no public exploit code.

Affected product: LogCenter V100R001C10. 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-8671/ (Markdown: https://insights.sbomify.com/CVE-2015-8671/index.md)
```

## Sources

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

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