ResteasyApplication · Redhat
CVE-2016-6346
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 · uneditedRESTEasy enables GZIPInterceptor, which allows remote attackers to cause a denial of service via unspecified vectors.
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 confidenceRESTEasy framework ships with GZIPInterceptor enabled by default, which handles Accept-Encoding: gzip headers. The vulnerability allows remote attackers to cause denial of service through the GZIP interceptor, likely via decompression bombs or resource exhaustion attacks that consume excessive CPU or memory during gzip decompression.
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
ResteasyApplication
all versionsCVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify RESTEasy installationSearch for resteasy*.jar files in the application lib/classpath, or check pom.xml/build.gradle for resteasy dependenciesAffected if RESTEasy framework is present in the environment
-
Verify GZIPInterceptor is loadedExamine the web.xml deployment descriptor for a filter or interceptor class named GZIPInterceptor, GZIPEnabler, or similar gzip-related filter. Also check RESTEasy provider configuration files for org.jboss.resteasy.plugins.interceptors.GZIPInterceptorAffected if A GZIP-related interceptor or filter is configured and active in the deployment
-
Check Accept-Encoding header handlingReview the application server or RESTEasy configuration for explicit enabling/disabling of gzip decompression. Look for properties such as resteasy.gzip.enabled, gzip.enabled, or similar that control Accept-Encoding: gzip processingAffected if GZIP handling is explicitly enabled or uses default settings (no explicit disable found)
-
Inspect resource consumption under gzip loadSend a request with Accept-Encoding: gzip header containing a small compressed payload to observe server resource usage. Alternatively, check if the server logs show heavy CPU/memory activity during compressed request processingAffected if The server processes gzip-encoded requests without size limits or resource guards
If RESTEasy is present with default GZIPInterceptor configuration enabled, the environment is vulnerable to resource exhaustion through gzip decompression attacks.
Generated from the published advisory. Verify against your own configuration.
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 dataDisable or properly configure the GZIPInterceptor in RESTEasy, or upgrade to a patched version of RESTEasy that addresses this vulnerability.
Fix this in Resteasy
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6346 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-6346 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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