# CVE-2020-25633: Generation of Error Message Containing Sensitive Information in RESTEasy client > RESTEasy client users can obtain sensitive server information via WebApplicationException, compromising data confidentiality. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 18 Sep 2020 - **Updated:** 4 Aug 2024 - **Also known as:** DEBIAN-CVE-2020-25633, GHSA-hr32-mgpm-qf2f, UBUNTU-CVE-2020-25633 ## What is CVE-2020-25633? CVE-2020-25633 is a medium-severity vulnerability in Red Hat resteasy-client, published on 18 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A 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. Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information) ## Which versions are affected by CVE-2020-25633? 8 open source packages ship an affected version, including org.jboss.resteasy:resteasy-client and org.jboss.resteasy:resteasy-client-microprofile. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.jboss.resteasy:resteasy-client` | Maven | All versions | 3.14.0.Final | | `org.jboss.resteasy:resteasy-client` | Maven | All versions | 3.14.0.Final | | `org.jboss.resteasy:resteasy-client` | Maven | From 4.0.0 | 4.5.7.Final | | `org.jboss.resteasy:resteasy-client` | Maven | From 4.0.0 | 4.5.7.Final | | `org.jboss.resteasy:resteasy-client-microprofile` | Maven | All versions | 3.14.0.Final | | `org.jboss.resteasy:resteasy-client-microprofile` | Maven | All versions | 3.14.0.Final | | `org.jboss.resteasy:resteasy-client-microprofile` | Maven | From 4.0.0 | 4.5.7.Final | | `org.jboss.resteasy:resteasy-client-microprofile` | Maven | From 4.0.0 | 4.5.7.Final | Products: Quarkus Quarkus, Redhat Resteasy. ## How do I fix CVE-2020-25633? Upgrade org.jboss.resteasy:resteasy-client to a fixed version for your release line: 3.14.0.Final or 4.5.7.Final. ## Is CVE-2020-25633 being exploited? There is no known exploitation of CVE-2020-25633 in the wild and no public exploit code. ## Other vulnerabilities in Red Hat resteasy-client - [CVE-2022-4116](https://insights.sbomify.com/CVE-2022-4116/): Code injection in quarkus dev ui config editor (critical 9.8) - [CVE-2022-2466](https://insights.sbomify.com/CVE-2022-2466/): Quarkus does not terminate HTTP requests header context (critical 9.8) - [CVE-2024-12225](https://insights.sbomify.com/CVE-2024-12225/): Io.quarkus:quarkus-security-webauthn: quarkus webauthn unexpected authentication bypass (critical 9.1) - [CVE-2026-39852](https://insights.sbomify.com/CVE-2026-39852/): Quarkus authorization bypass via semicolon path normalization inconsistency (high 8.8) - [CVE-2022-0981](https://insights.sbomify.com/CVE-2022-0981/): Privilege escalation in quarkus (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-25633 and fix it if it is affected. What it is: CVE-2020-25633 is a medium-severity vulnerability in Red Hat resteasy-client, published on 18 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-25633 in the wild and no public exploit code. Affected packages and fixed versions: - org.jboss.resteasy:resteasy-client (Maven): affected all versions; fixed in 3.14.0.Final - org.jboss.resteasy:resteasy-client (Maven): affected all versions; fixed in 3.14.0.Final - org.jboss.resteasy:resteasy-client (Maven): affected from 4.0.0; fixed in 4.5.7.Final - org.jboss.resteasy:resteasy-client (Maven): affected from 4.0.0; fixed in 4.5.7.Final - org.jboss.resteasy:resteasy-client-microprofile (Maven): affected all versions; fixed in 3.14.0.Final - org.jboss.resteasy:resteasy-client-microprofile (Maven): affected all versions; fixed in 3.14.0.Final - org.jboss.resteasy:resteasy-client-microprofile (Maven): affected from 4.0.0; fixed in 4.5.7.Final - org.jboss.resteasy:resteasy-client-microprofile (Maven): affected from 4.0.0; fixed in 4.5.7.Final Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2020-25633/ (Markdown: https://insights.sbomify.com/CVE-2020-25633/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-25633 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-25633 - OSV: https://osv.dev/vulnerability/CVE-2020-25633 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-25633/ Summaries are generated and may contain mistakes; the official description above is the record.