CVE-2019-11808

CVE-2019-11808 is a low-severity vulnerability in Ratpack Project Ratpack with a CVSS 3.x base score of 3.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-338.

Key facts

Description

Ratpack versions before 1.6.1 generate a session ID using a cryptographically weak PRNG in the JDK's ThreadLocalRandom. This means that if an attacker can determine a small window for the server start time and obtain a session ID value, they can theoretically determine the sequence of session IDs.

Frequently asked questions

What is CVE-2019-11808?
Ratpack versions before 1.6.1 generate a session ID using a cryptographically weak PRNG in the JDK's ThreadLocalRandom. This means that if an attacker can determine a small window for the server start time and obtain a session ID value, they can theoretically determine the sequence of session IDs.
How severe is CVE-2019-11808?
CVE-2019-11808 has a CVSS 3.x base score of 3.7, rated low severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2019-11808 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (67th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-11808?
CVE-2019-11808 affects Ratpack Project Ratpack. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2019-11808?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2019-11808 published?
CVE-2019-11808 was published on 2019-05-07 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Ratpack Project Ratpack

All CVEs affecting Ratpack Project Ratpack →

Other CWE-338 vulnerabilities

Browse all CWE-338 vulnerabilities →