CVE-2019-11808
No known exploitation. EPSS puts it in the 71st percentile. Fixed in 1.6.1.
What to do
Find your product and version, then upgrade to the build on the right.
- Maven io.ratpack:ratpack-sessionAffected: < 1.6.1Upgrade to: 1.6.1Stated by: GitHub advisory
- Maven io.ratpack:ratpack-javaAffected: < 1.6.1Upgrade to: 1.6.1Stated by: GitHub advisory
- Maven io.ratpack:ratpack-groovyAffected: < 1.6.1Upgrade to: 1.6.1Stated by: GitHub advisory
- Ratpack Project RatpackAffected: < 1.6.1Upgrade to: 1.6.1Stated by: NVD
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
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.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
1.3% chance of exploitation activity in the next 30 days, which ranks it in the 71st percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
4 events over 2025 days, from the signal feeds we watch.
- Patch availablerecord updated
- Publishedweakness classified
Affected products
Technical detail
CVSS 3.0 vector
Open in the CVSS calculatorCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Scored 3.7 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality LowSome restricted information is disclosed, but limited in scope
- Integrity NoneNo integrity impact
- Availability NoneNo availability impact
Weaknesses
Sources
References in the record
- github.com/ratpack/ratpack/commit/f2b63eb82dd71194319fd3945f5edf29b8f3a42d
- github.com/ratpack/ratpack/issues/1448
- github.com/ratpack/ratpack/releases/tag/v1.6.1
And 1 more reference. See all after sign-in
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Maven, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI