Odoo OAuth Hijacking access control

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.3$0-$5k0.00

Summaryinfo

A vulnerability was found in Odoo. It has been rated as critical. The impacted element is an unknown function of the component OAuth. This manipulation causes access control (Hijacking). This vulnerability appears as CVE-2017-10805. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability classified as critical was found in Odoo (Customer Relationship Management System) (version unknown). Affected by this vulnerability is an unknown function of the component OAuth. The manipulation with an unknown input leads to a access control vulnerability (Hijacking). The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

In Odoo 8.0, Odoo Community Edition 9.0 and 10.0, and Odoo Enterprise Edition 9.0 and 10.0, incorrect access control on OAuth tokens in the OAuth module allows remote authenticated users to hijack OAuth sessions of other users.

The bug was discovered 06/29/2017. The weakness was presented 07/04/2017 (GitHub Repository). The advisory is shared at github.com. This vulnerability is known as CVE-2017-10805 since 07/03/2017. The attack can be launched remotely. The successful exploitation requires a single authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 5 days. During that time the estimated underground price was around $0-$5k.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

See VDB-103032 and VDB-103031 for similar entries. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Name

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.6
VulDB Meta Temp Score: 7.3

VulDB Base Score: 6.3
VulDB Temp Score: 5.8
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 8.8
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Name: Hijacking
Class: Access control / Hijacking
CWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

06/29/2017 🔍
07/03/2017 +4 days 🔍
07/04/2017 +1 days 🔍
07/04/2017 +0 days 🔍
07/05/2017 +1 days 🔍
12/09/2022 +1983 days 🔍

Sourcesinfo

Product: github.com

Advisory: 17921
Status: Not defined
Confirmation: 🔍

CVE: CVE-2017-10805 (🔍)
GCVE (CVE): GCVE-0-2017-10805
GCVE (VulDB): GCVE-100-103033
See also: 🔍

Entryinfo

Created: 07/05/2017 09:14
Updated: 12/09/2022 16:28
Changes: 07/05/2017 09:14 (57), 10/22/2019 09:39 (2), 12/09/2022 16:28 (4)
Complete: 🔍
Cache ID: 216:D46:103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!