CVE-2018-14733
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 · uneditedThe Odoo Community Association (OCA) dbfilter_from_header module makes Odoo 8.x, 9.x, 10.x, and 11.x vulnerable to ReDoS (regular expression denial of service) under certain circumstances.
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 · moderate confidenceThe Odoo dbfilter_from_header module contains a ReDoS vulnerability where malicious or specially crafted HTTP header input can cause the regular expression engine to consume excessive CPU resources, leading to denial of service. The vulnerability stems from an inefficient regex pattern that exhibits catastrophic backtracking when processing certain input strings.
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= 8.0= 9.0= 10.0= 11.0CVSS 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.0/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 installed Odoo versionAccess Odoo about page or check version file; compare against affected versions 8.0, 9.0, 10.0, 11.0Affected if version matches 8.0, 9.0, 10.0, or 11.0
-
Locate dbfilter_from_header moduleSearch Odoo modules directory for dbfilter_from_header or inspect installed modules list via Odoo interface or command lineAffected if module files are present in the Odoo installation
-
Verify dbfilter_from_header is loadedCheck Odoo loaded modules or apps list for dbfilter_from_header being listed as installed or enabledAffected if module appears as installed or enabled in Odoo
-
Confirm HTTP header filtering is activeInspect Odoo configuration files or settings for dbfilter_from_header related configuration such as dbfilter using header valuesAffected if dbfilter_from_header is configured to process HTTP headers for database filtering
-
Inspect regex pattern in dbfilter_from_headerExamine the source code of dbfilter_from_header module for regex patterns used in header processing; look for patterns that may exhibit catastrophic backtrackingAffected if inefficient regex patterns are found in the module code handling HTTP header input
Environment is affected if running Odoo 8.0-11.0 with the dbfilter_from_header module installed and enabled, where HTTP header-based database filtering is actively configured.
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 dataApply available patches for the dbfilter_from_header module, or implement regex timeout controls and input validation on header processing to prevent ReDoS exploitation. Consider disabling the module if not required in production environments.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14733 — 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-2018-14733 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