Docker Desktop 4.11.x IPC Response trust boundary violation

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.1$0-$5k0.00

Summaryinfo

A vulnerability was found in Docker Desktop 4.11.x. It has been rated as critical. Affected by this vulnerability is an unknown functionality of the component IPC Response Handler. The manipulation leads to trust boundary violation. This vulnerability is uniquely identified as CVE-2023-0627. Local access is required to approach this attack. No exploit exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Docker Desktop 4.11.x (Virtualization Software). It has been rated as critical. This issue affects an unknown function of the component IPC Response Handler. The manipulation with an unknown input leads to a trust boundary violation vulnerability. Using CWE to declare the problem leads to CWE-501. The product mixes trusted and untrusted data in the same data structure or structured message. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Docker Desktop 4.11.x allows --no-windows-containers flag bypass via IPC response spoofing which may lead to Local Privilege Escalation (LPE).This issue affects Docker Desktop: 4.11.X.

The weakness was disclosed 09/25/2023. The advisory is shared at docs.docker.com. The identification of this vulnerability is CVE-2023-0627 since 02/01/2023. Neither technical details nor an exploit are publicly available.

Upgrading to version 4.12.0 eliminates this vulnerability. The upgrade is hosted for download at docs.docker.com.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.2
VulDB Meta Temp Score: 7.1

VulDB Base Score: 7.0
VulDB Temp Score: 6.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.8
NVD Vector: 🔍

CNA Base Score: 6.7
CNA Vector (Docker Inc.): 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Trust boundary violation
CWE: CWE-501
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

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: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Desktop 4.12.0

Timelineinfo

02/01/2023 🔍
09/25/2023 +235 days 🔍
09/25/2023 +0 days 🔍
10/16/2023 +21 days 🔍

Sourcesinfo

Advisory: docs.docker.com
Status: Confirmed

CVE: CVE-2023-0627 (🔍)
GCVE (CVE): GCVE-0-2023-0627
GCVE (VulDB): GCVE-100-240317

Entryinfo

Created: 09/25/2023 19:46
Updated: 10/16/2023 09:37
Changes: 09/25/2023 19:46 (51), 10/16/2023 09:37 (11)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!