Shelly 4PM Pro Four-Channel Smart Switch 0.11.0 BLE out-of-bounds

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

Summaryinfo

A vulnerability described as problematic has been identified in Shelly 4PM Pro Four-Channel Smart Switch 0.11.0. This issue affects some unknown processing of the component BLE. Executing a manipulation can lead to out-of-bounds. The identification of this vulnerability is CVE-2023-33383. The attack can only be executed locally. Furthermore, there is an exploit available.

Detailsinfo

A vulnerability classified as problematic was found in Shelly 4PM Pro Four-Channel Smart Switch 0.11.0. This vulnerability affects an unknown code block of the component BLE. The manipulation with an unknown input leads to a out-of-bounds vulnerability. The CWE definition for the vulnerability is CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect availability. CVE summarizes:

Shelly 4PM Pro four-channel smart switch 0.11.0 allows an attacker to trigger a BLE out of bounds read fault condition that results in a device reload.

The weakness was shared 08/02/2023. The advisory is available at exploitsecurity.io. This vulnerability was named CVE-2023-33383 since 05/22/2023. Technical details are unknown but a public exploit is available.

It is possible to download the exploit at exploitsecurity.io. It is declared as proof-of-concept.

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

The vulnerability is also documented in the databases at Exploit-DB (51657) and EUVD (EUVD-2023-37546). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.9
VulDB Meta Temp Score: 3.8

VulDB Base Score: 2.5
VulDB Temp Score: 2.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.3
NVD Vector: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Out-of-bounds
CWE: CWE-125 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Exploit-DB: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

05/22/2023 🔍
08/02/2023 +72 days 🔍
08/02/2023 +0 days 🔍
01/04/2026 +886 days 🔍

Sourcesinfo

Advisory: 173954
Status: Not defined

CVE: CVE-2023-33383 (🔍)
GCVE (CVE): GCVE-0-2023-33383
GCVE (VulDB): GCVE-100-235954
EUVD: 🔍
scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 08/02/2023 19:44
Updated: 01/04/2026 10:20
Changes: 08/02/2023 19:44 (41), 08/24/2023 14:13 (1), 08/24/2023 14:15 (11), 07/04/2024 09:56 (15), 01/04/2026 10:20 (2)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

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!