CVE-2020-25724

A flaw was found in RESTEasy, where an incorrect response to an HTTP request is provided. This flaw allows an attacker to gain access to privileged information. The highest threat from this vulnerability is to confidentiality and integrity. Versions before resteasy 2.0.0.Alpha3 are affected.

Published: 2021-05-26 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2020-25724 is rated Low Risk (33.5/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.63%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2020-25724

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.13% 0.63% +0.50%
2 2025-03-30 0.45% 0.13% -0.32%
3 2025-03-29 0.45%

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-25724

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
2.8 1.4 [email protected]
4.0 2.0 MEDIUM
AV:N/AC:L/Au:S/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
8.0 2.9 [email protected]

Weakness enumeration for CVE-2020-25724

GitHub Security Advisory for CVE-2020-25724

GHSA-9699-gm7f-cmjv · Severity: medium · Ecosystem: maven — Unsynchronized Access to Shared Data in a Multithreaded Context in RESTEasy

OS Trackers for CVE-2020-25724

vendor priority summary link
debian unimportant CVE-2020-25724 unimportant priority: Debian including 2 source packages (resteasy, resteasy3.0), 6 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 6. https://security-tracker.debian.org/tracker/CVE-2020-25724
redhat medium https://access.redhat.com/security/cve/CVE-2020-25724
ubuntu medium CVE-2020-25724 medium priority: Ubuntu including 2 source packages (resteasy, resteasy3.0), 28 status rows across 14 suites (bionic, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, trusty, upstream, xenial): ignored 12, not-affected 10, DNE 4, released 2. https://ubuntu.com/security/CVE-2020-25724

Affected software / configurations for CVE-2020-25724

Vendor Product Version Raw CPE
redhat resteasy < 2.0.0 cpe:2.3:a:redhat:resteasy:*:*:*:*:*:*:*:*
redhat resteasy 2.0.0 cpe:2.3:a:redhat:resteasy:2.0.0:alpha1:*:*:*:*:*:*
redhat resteasy 2.0.0 cpe:2.3:a:redhat:resteasy:2.0.0:alpha2:*:*:*:*:*:*
quarkus quarkus < 1.11.2 cpe:2.3:a:quarkus:quarkus:*:*:*:*:*:*:*:*

References for CVE-2020-25724

cvelogic Threat Intelligence