ResteasyApplication · Redhat
CVE-2020-25633
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 · uneditedA flaw was found in RESTEasy client in all versions of RESTEasy up to 4.5.6.Final. It may allow client users to obtain the server's potentially sensitive information when the server got WebApplicationException from the RESTEasy client call. The highest threat from this vulnerability is to data confidentiality.
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 confidenceA flaw in RESTEasy client (versions up to 4.5.6.Final) allows client users to obtain potentially sensitive server information when the server throws a WebApplicationException during a RESTEasy client call. This occurs because exception handling may expose server-side details to the client, compromising data confidentiality.
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
< 3.14.0>= 4.5.0, <= 4.5.6<= 1.11.6CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Identify RESTEasy client dependency in your build configurationSearch your project's build files (pom.xml, build.gradle, package.json) for 'resteasy-client' or 'quarkus-resteasy-client' dependencies and note the exact versionAffected if The version matches < 3.14.0, OR >= 4.5.0 AND <= 4.5.6 for resteasy-client, OR <= 1.11.6 for quarkus dependencies
-
Locate all JAR files containing resteasy-clientSearch your application deployment (WAR, EAR, JAR, or lib directory) for JAR files with 'resteasy-client' in the filename and check the manifest or filename for version informationAffected if The version is below 3.14.0 or between 4.5.0 and 4.5.6 inclusive
-
Identify if your code uses RESTEasy client APISearch source code for imports of 'javax.ws.rs.client' packages or 'org.jboss.resteasy.client' classes, specifically ClientBuilder, WebTarget, or RESTClient proxiesAffected if Code imports or uses RESTEasy client API and the dependency version is vulnerable
-
Check for custom ExceptionMapper implementationsSearch for classes implementing javax.ws.rs.ext.ExceptionMapper interface, especially those handling WebApplicationExceptionAffected if Custom ExceptionMapper exists but does not explicitly sanitize exception details before returning response to client
-
Verify exception handling in client-side codeInspect code that makes RESTEasy client calls (using ClientBuilder, WebTarget, or @RESTClient interfaces) and check if response.getEntity() or similar methods expose raw exception detailsAffected if Client code processes responses without filtering server-returned exception information
You are affected if your application uses RESTEasy client (resteasy-client or quarkus-resteasy-client) with version < 3.14.0 or >= 4.5.0 through 4.5.6, and the server can return WebApplicationException responses that your client code processes without sanitization.
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 data3.14.0
Upgrade RESTEasy to a version beyond 4.5.6.Final and ensure custom exception mappers properly sanitize error responses to prevent sensitive information leakage.
Fix this in Resteasy
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25633 — 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-2020-25633 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