Integration Camel KApplication · Redhat
CVE-2020-14326
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability was found in RESTEasy, where RootNode incorrectly caches routes. This issue results in hash flooding, leading to slower requests with higher CPU time spent searching and adding the entry. This flaw allows an attacker to cause a denial of service.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceRESTEasy's RootNode incorrectly caches routes using a hash-based data structure vulnerable to hash flooding. Attackers can exploit hash collisions to degrade lookup performance from O(1) to O(n), causing slower requests and elevated CPU consumption that leads to denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Integration Camel KApplication
all versions
ResteasyApplication
>= 4.2.0, < 4.5.6all versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify RESTEasy library versionLocate resteasy-core or jboss-resteasy JAR files in your application classpath or dependencies (pom.xml, build.gradle, lib directory). Check the JAR filename or MANIFEST.MF for the version number.Affected if The version is >= 4.2.0 and < 4.5.6
-
Verify RESTEasy is in useCheck if your application exposes RESTful HTTP endpoints - look for @Path annotations, JAX-RS imports (javax.ws.rs.*), or REST controller classes in your codebase.Affected if RESTEasy is used to handle REST requests and the version is vulnerable
-
Check for Redhat Camel K installationIf you use Redhat Integration Camel K, check the installed version via 'kamel version' command or Kubernetes deployment manifests.Affected if Any version of Redhat Camel K is in use
-
Check for Netapp Oncommand InsightVerify if Netapp Oncommand Insight software is installed in your environment by checking installed packages or running 'oci' commands if available.Affected if Netapp Oncommand Insight is installed (all versions affected)
-
Confirm hash-based routing is enabledRESTEasy uses RootNode with hash-based routing by default. Check if your application initializes RESTEasy JAX-RS resources - the vulnerability applies when REST endpoints are registered.Affected if RESTEasy JAX-RS resources are registered and the version is in the affected range
You are affected if RESTEasy version 4.2.0 through 4.5.5 is in use, or if Redhat Camel K or Netapp Oncommand Insight is deployed, as these use the vulnerable hash-based routing implementation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data4.5.6
Update RESTEasy to a patched version that implements hash randomization or use a hash table implementation with randomized seeding. Implement request rate limiting as a compensating control until the update is applied.
Fix this in Integration Camel K
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14326 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-14326 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data