ResteasyApplication · Redhat
CVE-2016-6348
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 · uneditedJacksonJsonpInterceptor in RESTEasy might allow remote attackers to conduct a cross-site script inclusion (XSSI) attack.
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 · low confidenceJacksonJsonpInterceptor in RESTEasy contains a vulnerability that could enable cross-site script inclusion (XSSI) attacks, allowing malicious external sites to potentially include JSON responses from the affected RESTEasy application via script tags and read sensitive data.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify RESTEasy installationSearch for resteasy*.jar files in the application deployment directory, or check Maven/Gradle dependencies for resteasy-groupId artifactsAffected if RESTEasy libraries are found in the runtime environment
-
Locate JacksonJsonpInterceptor classSearch for JacksonJsonpInterceptor class in the application classpath or examine RESTEasy configuration files for jsonp-enabled interceptorsAffected if JacksonJsonpInterceptor is registered or the jsonp provider is enabled in RESTEasy configuration
-
Identify exposed JSONP endpointsReview REST endpoint definitions for @Produces("application/javascript") or endpoint parameters named 'callback', 'jsonp', or similar JSONP callback parametersAffected if Application exposes endpoints that return JSONP responses (JavaScript MIME type) or accepts callback parameters
-
Check for Origin/Referer validation on JSONP responsesInspect web.xml or RESTEasy filter/interceptor configuration for CORS filters or origin header validation logic applied to JSONP endpointsAffected if No origin header validation, Referer checking, or CORS policy is configured for JSONP endpoints
The environment is affected if RESTEasy with JacksonJsonpInterceptor is in use and JSONP endpoints are exposed without Origin/Referer header validation or CORS controls.
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 dataUpdate RESTEasy to a patched version and implement anti-XSSI controls such as Origin/Referer header validation, CSRF token requirements, or strict CORS policies on JSONP endpoints.
Fix this in Resteasy
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6348 — 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-6348 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