CVE-2023-33383 json
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 de…
published 2023-08-02 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-37546
- cvss
- 5.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.7%
- EPSS 4.7% chance of exploitation in 30 days, percentile 91%
- public exploits
- 1
- Exploit-DB
Summary
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.
Timeline
- Published
- First public exploit (EDB-51657)
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
4.73% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-51657 Shelly PRO 4PM v0.11.0 - Authentication Bypass remote, 2023-08-04
- exploitsecurity.io https://www.exploitsecurity.io/post/cve-2023-33383-authentication-bypass-via-an-out-of-bounds-read-vulnerability referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/173954/Shelly-PRO-4PM-0.11.0-Authentication-Bypass.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
Affected products
- shelly pro_4pm
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
References
-
exploitsecurity.io
/post/cve-2023-33383-authentication-bypass-via-an-out-of-bounds-read-vulnerability
exploit, third-party-advisory
-
packetstormsecurity.com
/files/173954/Shelly-PRO-4PM-0.11.0-Authentication-Bypass.html
exploit, third-party-advisory, vdb-entry
Sources
- CVE List CVE-2023-33383
- NVD CVE-2023-33383
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.