LIXIL My SATIS Genius Toilet Application on Android Bluetooth PIN improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in LIXIL My SATIS Genius Toilet Application on Android. Impacted is an unknown function of the component Bluetooth PIN. The manipulation leads to improper authentication. This vulnerability is documented as CVE-2013-4866. Additionally, an exploit exists.
Details
A vulnerability, which was classified as critical, has been found in LIXIL My SATIS Genius Toilet Application on Android (Android App Software) (the affected version is unknown). This issue affects an unknown code of the component Bluetooth PIN. The manipulation with an unknown input leads to a improper authentication vulnerability. Using CWE to declare the problem leads to CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
The LIXIL Corporation My SATIS Genius Toilet application for Android has a hardcoded Bluetooth PIN, which allows physically proximate attackers to trigger physical resource consumption (water or heat) or user discomfort.
The weakness was released 04/16/2015 (Website). The advisory is shared at seclists.org. The identification of this vulnerability is CVE-2013-4866 since 07/17/2013. The attack needs to be initiated within the local network. No form of authentication is needed for a successful exploitation. Technical details are unknown but a public exploit is available.
The exploit is available at packetstormsecurity.com. 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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/17/2013 🔍04/16/2015 🔍
04/16/2015 🔍
04/17/2015 🔍
06/24/2024 🔍
Sources
Advisory: 122655Status: Not defined
CVE: CVE-2013-4866 (🔍)
GCVE (CVE): GCVE-0-2013-4866
GCVE (VulDB): GCVE-100-74981
scip Labs: https://www.scip.ch/en/?labs.20130704
Entry
Created: 04/17/2015 10:24Updated: 06/24/2024 03:28
Changes: 04/17/2015 10:24 (45), 01/20/2019 13:27 (3), 05/09/2022 08:20 (3), 06/24/2024 03:28 (23)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.