# CVE-2016-8627: Denial of service in admin-cli

> An attacker can trigger a user's browser to download server logs via GET requests, consuming resources and impairing normal server functioning.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 May 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wmq3-659r-46hg

## What is CVE-2016-8627?

CVE-2016-8627 is a medium-severity denial of service vulnerability in Redhat Jboss Enterprise Application Platform, published on 11 May 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

admin-cli before versions 3.0.0.alpha25, 2.2.1.cr2 is vulnerable to an EAP feature to download server log files that allows logs to be available via GET requests making them vulnerable to cross-origin attacks. An attacker could trigger the user's browser to request the log files consuming enough resources that normal server functioning could be impaired.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2016-8627?

It affects 2 products.


Products: Redhat Jboss Enterprise Application Platform, Redhat Keycloak.

## How do I fix CVE-2016-8627?

Upgrade to a fixed version.

## Is CVE-2016-8627 being exploited?

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

## Other vulnerabilities in Redhat Jboss Enterprise Application Platform

- [CVE-2017-12149](https://insights.sbomify.com/CVE-2017-12149/): Red Hat JBoss Application Server Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2010-1428](https://insights.sbomify.com/CVE-2010-1428/): Red Hat JBoss Information Disclosure (medium 5.9, exploited in the wild)
- [CVE-2010-0738](https://insights.sbomify.com/CVE-2010-0738/): Red Hat JBoss Authentication Bypass (low 3.7, exploited in the wild)
- [CVE-2016-3690](https://insights.sbomify.com/CVE-2016-3690/): Deserialization in n/a (critical 9.8)
- [CVE-2017-7504](https://insights.sbomify.com/CVE-2017-7504/): Deserialization in JBoss (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-8627 and fix it if it is affected.

What it is: CVE-2016-8627 is a medium-severity denial of service vulnerability in Redhat Jboss Enterprise Application Platform, published on 11 May 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-8627 in the wild and no public exploit code.

Affected product: Redhat Jboss Enterprise Application Platform. 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-2016-8627/ (Markdown: https://insights.sbomify.com/CVE-2016-8627/index.md)
```

## Sources

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

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