Security readout for executives and security teams
Plain-English summary
This flaw affects older Odoo releases and can let a logged-in remote user hijack another user’s OAuth session. That can turn ordinary account access into impersonation risk. The public bundle does not provide CVSS, CWE, patch details, or evidence of active exploitation.
Executive priority
Prioritize assessment if Odoo is business-critical, externally accessible, or used for sensitive workflows. The impact is potentially serious because session hijacking can enable impersonation, but urgency cannot be fully rated from the supplied sources.
Technical view
CVE-2017-10805 is an incorrect access control issue in Odoo’s OAuth module. The stated affected versions are Odoo 8.0, Odoo Community Edition 9.0 and 10.0, and Odoo Enterprise Edition 9.0 and 10.0. A remote authenticated user may hijack OAuth sessions belonging to other users.
Likely exposure
Exposure is most likely in organizations still running the named Odoo versions with the OAuth module in use. Internet-facing or broadly accessible Odoo instances increase concern because the attacker only needs authenticated access, not administrative access.
Exploitation context
The source bundle says exploitation requires a remote authenticated user. It does not cite public exploit activity, KEV listing, exploit code, or active abuse. Treat exploitation status as unconfirmed based on the provided evidence.
Researcher notes
The provided record lacks CVSS, CWE classification, detailed affected CPEs, and patch metadata. Analysis should stay anchored to the CVE description and Odoo issue reference. Do not assume unauthenticated exploitation or confirmed public exploitation.
Mitigation direction
- Inventory Odoo 8.0, CE 9.0/10.0, and EE 9.0/10.0 deployments.
- Check Odoo issue #17921 and vendor channels for fixed versions or guidance.
- Prioritize vendor-supported upgrades if affected legacy versions are found.
- Limit authenticated Odoo access to trusted users during assessment.
- Review OAuth and session logs for unusual cross-user activity.
Validation and detection
- Confirm deployed Odoo edition and version against the affected list.
- Determine whether the OAuth module is installed or enabled.
- Review OAuth token access controls without attempting session hijacking.
- Check logs for OAuth token use inconsistent with the account owner.
- Verify vendor-recommended fixes or upgrades are applied when identified.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2017-10805 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/odoo/odoo/issues/17921CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.