dbcve.org
Jboss Enterprise Application PlatformApplication · Redhat

CVE-2016-7046

MEDIUM · 5.9 CVSS v3.0 Published 2016-10-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Red Hat JBoss Enterprise Application Platform (EAP) 7, when operating as a reverse-proxy with default buffer sizes, allows remote attackers to cause a denial of service (CPU and disk consumption) via a long URL.

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 · moderate confidence

JBoss EAP 7, when configured as a reverse proxy with default buffer sizes, allows remote attackers to cause denial of service by sending long URLs that exhaust CPU and disk resources. The default Undertow buffer configuration is insufficient to handle maliciously large requests.

MitigationConfigure appropriate buffer sizes in the Undertow subsystem or reverse proxy configuration to handle large request headers/URLs, and implement request size limits to prevent resource exhaustion.

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:= 7.0

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/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 JBoss EAP installation and version
    Check for JBoss EAP 7.0 installation directories (e.g., /opt/jboss-eap-7.0, $JBOSS_HOME) and inspect version files or run 'jboss-cli.sh --version' if available. Alternatively, look for 'JBoss Enterprise Application Platform' or 'EAP 7.0' strings in startup scripts or manifest files.
    Affected if The installed version is JBoss EAP 7.0 (exact version 7.0) and no patches have been applied.
  2. Locate Undertow subsystem configuration
    In the JBoss EAP configuration directory, locate the standalone.xml or domain.xml configuration file. Search for the '<subsystem xmlns="urn:jboss:domain:undertow:...">' section. This is typically found in $JBOSS_HOME/standalone/configuration/standalone.xml or the corresponding domain configuration.
    Affected if Undertow subsystem is present in the configuration (which is default for EAP 7).
  3. Check for reverse proxy configuration in Undertow
    Within the Undertow subsystem XML, look for elements such as '<reverse-proxy>', '<host>', or handler configurations that indicate reverse proxy or load balancer functionality. Search for 'reverse-proxy' or 'mod-cluster' related configuration blocks.
    Affected if A reverse proxy handler or host configuration is defined in the Undertow subsystem.
  4. Inspect Undertow buffer pool and buffer size settings
    Within the Undertow subsystem, look for '<buffer-pool>' elements and check for 'buffer-size' attributes. Also examine the default servlet-container settings. If no explicit buffer-size is defined or if values appear to be at defaults, the system may be vulnerable. Look for entries like '<buffer-pool name="default" buffer-size="1024" ...>' or similar.
    Affected if No explicit buffer-size is configured, or buffer sizes are set to default/low values (e.g., 1024 bytes or similar small sizes).
  5. Check for request size limits on the server
    Search the Undertow configuration for '<max-request-size>' or similar request limiting attributes on servlet-container or host definitions. Also check for any 'max-header-size' or 'max-body-size' configurations that may limit URL lengths.
    Affected if No request size limits are defined, or limits are set very high allowing arbitrarily large URLs.

A system is affected if it runs JBoss EAP 7.0 with Undertow configured as a reverse proxy using default or insufficient buffer sizes and no request size limits are enforced, allowing long URLs to exhaust resources.

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

Configure appropriate buffer sizes in the Undertow subsystem or reverse proxy configuration to handle large request headers/URLs, and implement request size limits to prevent resource exhaustion.

Fix this in Jboss Enterprise Application Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-7046 — 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-7046 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