Meari SDK hardcoded cryptographic keys
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Meari | com.meari.sdk | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Meari | Com.meari.sdk |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.241% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Meari
Meari com.meari.sdk |
|
| Vendors & Products |
Meari
Meari com.meari.sdk |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In Meari IoT SDK builds embedded in CloudEdge 5.5.0 (build 220), Arenti 1.8.1 (build 220), and white-label Android apps <= 1.8.x (latest observed), multiple security-critical secrets are hardcoded and shared, including API signing material, password-transport keying, and service access keys. | |
| Title | Meari SDK hardcoded cryptographic keys | |
| Weaknesses | CWE-321 | |
| References |
| |
| Metrics |
cvssV3_1
|