dbcve.org
Jboss Enterprise Application PlatformApplication · Redhat

CVE-2016-8627

MEDIUM · 6.5 CVSS v3.0 Published 2018-05-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The admin-cli component contains a vulnerability in its EAP feature that allows server log files to be downloaded via GET requests without proper access controls. This makes the logs vulnerable to cross-origin attacks where an attacker can trigger a user's browser to repeatedly request log files, consuming server resources and potentially impairing normal server functioning.

MitigationUpgrade admin-cli to version 3.0.0.alpha25 or later (or 2.2.1.cr2), and implement proper access controls and CSRF protections on log file download endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Jboss Enterprise Application PlatformApplication
Affected:= 6.4.0= 7.0.0= 7.1.0
KeycloakApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed JBoss EAP or Keycloak version
    Check the product version by examining the server installation directory, startup logs, or management console. For JBoss EAP, look in $JBOSS_HOME/modules/system/layers/base/.system.snap/ or check the version.txt file. For Keycloak, check the version in the startup logs or the bin/standalone.sh script.
    Affected if The installed version matches 6.4.0, 7.0.0, 7.1.0 for JBoss EAP, or any version for Keycloak.
  2. Verify admin-cli component presence
    Check if the admin-cli web application is deployed on the server. This is typically found in the deployments directory or can be listed via the JBoss/Keycloak management console.
    Affected if The admin-cli component is deployed and running on the server.
  3. Confirm EAP log download feature is enabled
    Examine the server configuration files (standalone.xml or domain.xml for JBoss, or keycloak.json for Keycloak) to determine if the EAP-based log viewing feature in admin-cli is configured and active.
    Affected if The EAP feature for log file access is enabled in the admin-cli configuration.
  4. Test log file download endpoint accessibility
    Using a web browser or HTTP client, attempt to access the log download endpoint through admin-cli (typically /admin-cli/logs or similar path) via a GET request without providing credentials. Also test from a cross-origin context (different domain).
    Affected if Log files can be downloaded via unauthenticated GET requests or cross-origin requests without proper access controls.

A system is affected if it runs a vulnerable JBoss EAP version (6.4.0, 7.0.0, 7.1.0) or any Keycloak version, has the admin-cli component deployed with the EAP log feature enabled, and allows unauthenticated or cross-origin access to log file downloads.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade admin-cli to version 3.0.0.alpha25 or later (or 2.2.1.cr2), and implement proper access controls and CSRF protections on log file download endpoints.

Fix this in Jboss Enterprise Application Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-8627 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-8627 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data