dbcve.org
Jboss Enterprise Application PlatformApplication · Redhat

CVE-2016-6311

MEDIUM · 5.3 CVSS v3.0 Published 2017-08-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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
Get requests in JBoss Enterprise Application Platform (EAP) 7 disclose internal IP addresses to remote attackers.

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

In JBoss Enterprise Application Platform 7, certain GET requests cause the application to disclose internal IP addresses in HTTP responses. This information disclosure occurs through response headers, error pages, or other output where internal network topology is revealed to remote attackers who send crafted GET requests.

MitigationConfigure JBoss EAP to use proper proxy handling and filter internal IP addresses from HTTP responses, or apply vendor-supplied patches. Review and restrict endpoint exposure to prevent unauthenticated attackers from triggering the disclosure.

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

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

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. Check JBoss EAP version
    Locate the jboss-eap-7.x installation directory and check the version file (such as version.txt or jboss-as-product.conf) or run the 'jboss-cli.sh' command and query the product version with 'read-attribute product-version'
    Affected if The installed version is exactly 7.0 (Red Hat JBoss Enterprise Application Platform 7.0)
  2. Verify HTTP endpoints are externally accessible
    Check the undertow subsystem configuration in the standalone.xml or domain.xml configuration file, looking at the <host> definitions under <undertow> <server> to determine if listeners are bound to non-localhost addresses or exposed through a public-facing interface
    Affected if HTTP listeners are bound to 0.0.0.0 or an external network interface, making the application reachable from remote clients
  3. Test for internal IP disclosure in response headers
    Send various crafted GET requests to the application's exposed endpoints (such as /, /admin, /console, or any other accessible path) and inspect all response headers using a tool like curl with the -v flag to examine server-generated headers
    Affected if Any response header (such as X-Forwarded-For, Server, or custom headers) contains private RFC1918 IP addresses (10.x.x.x, 172.16-31.x.x, 192.168.x.x) or internal network addresses
  4. Test for internal IP disclosure in error pages
    Send malformed or unexpected requests (such as invalid paths, malformed parameters, or requests triggering exceptions) and examine the generated error pages or default error handlers for exposed internal IP addresses
    Affected if Error responses or exception pages display internal IP addresses in stack traces, error messages, or diagnostic output
  5. Review proxy and load balancer configuration
    If JBoss EAP operates behind a proxy or load balancer, examine the proxy configuration settings and check for improper handling of X-Forwarded-For headers or other proxy-related headers that may be echoed back in responses
    Affected if Proxy headers are reflected in responses without proper filtering or the application directly exposes backend server IPs

A user is affected if they are running JBoss EAP version 7.0 with HTTP endpoints exposed to network access where internal IP addresses appear in any HTTP response headers or error output.

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 JBoss EAP to use proper proxy handling and filter internal IP addresses from HTTP responses, or apply vendor-supplied patches. Review and restrict endpoint exposure to prevent unauthenticated attackers from triggering the disclosure.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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