Summary
Jetty Uses Predictable Session Identifiers
Jetty before 4.2.27, 5.1 before 5.1.12, 6.0 before 6.0.2, and 6.1 before 6.1.0pre3 generates predictable session identifiers using java.util.random, which makes it easier for remote attackers to guess a session identifier through brute force attacks, bypass authentication requirements, and possibly conduct cross-site request forgery attacks.
Impact
Security-sensitive operations rely on values that are predictable or insufficiently random. Typical impact: forged tokens, guessable identifiers, or broken cryptographic protocols.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
org.eclipse.jetty:jetty-server to 4.2.27 or later; org.eclipse.jetty:jetty-server to 5.1.12 or later; org.eclipse.jetty:jetty-server to 6.0.2 or later; org.eclipse.jetty:jetty-server to 6.1.0pre3 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2006-6969? CVE-2006-6969 is a medium-severity use of insufficiently random values vulnerability in org.eclipse.jetty:jetty-server (maven), affecting versions < 4.2.27. It is fixed in 4.2.27, 5.1.12, 6.0.2, 6.1.0pre3. Security-sensitive operations rely on values that are predictable or insufficiently random.
- Which versions of org.eclipse.jetty:jetty-server are affected by CVE-2006-6969? org.eclipse.jetty:jetty-server (maven) versions < 4.2.27 is affected.
- Is there a fix for CVE-2006-6969? Yes. CVE-2006-6969 is fixed in 4.2.27, 5.1.12, 6.0.2, 6.1.0pre3. Upgrade to this version or later.
- Is CVE-2006-6969 exploitable, and should I be worried? Whether CVE-2006-6969 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2006-6969 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2006-6969?
- Upgrade
org.eclipse.jetty:jetty-serverto 4.2.27 or later - Upgrade
org.eclipse.jetty:jetty-serverto 5.1.12 or later - Upgrade
org.eclipse.jetty:jetty-serverto 6.0.2 or later - Upgrade
org.eclipse.jetty:jetty-serverto 6.1.0pre3 or later
- Upgrade