Com.Meari.Sdk
Approved changes feed: RSS · Atom
cpe:2.3:a:meari:com.meari.sdk:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Meari (cc37fbd5-cec5-5ab9-8472-1b3eab11dd16) |
|---|---|
| Product | Com.Meari.Sdk (1aee2edd-07fe-5f79-9037-8e31ff57a44d) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-33362 |
vulnerable | 2026-06-08 07:59:09.772833 |
Meari SDK hardcoded cryptographic keys
HIGH (8.6)
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.
Published: 2026-05-11T16:04:16.704Z
Updated: 2026-05-11T18:15:45.783Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-33361 |
vulnerable | 2026-06-08 07:59:09.772526 |
Meari weak XOR obfuscation
HIGH (7.5)
In Meari IoT SDK image handling (libmrplayer.so) as observed in CloudEdge 5.5.0 (build 220), Arenti 1.8.1 (build 220), and related white-label apps (<= 1.8.x), baby monitor ".jpgx3" files use reversible XOR over only the first 1024 bytes with a predictable key derivation model.
Published: 2026-05-11T16:03:55.746Z
Updated: 2026-05-11T18:17:43.933Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-33357 |
vulnerable | 2026-06-08 07:59:09.770736 |
Meari OpenAPI device status IDOR
HIGH (7.5)
In Meari client applications embedding "com.meari.sdk" (including CloudEdge 5.5.0 build 220, Arenti 1.8.1 build 220, and related white-label <= 1.8.x), the integrated call path to openapi-euce.mearicloud.com can be abused to retrieve WAN IP data for arbitrary devices. The root cause is a server-side authorization failure in "GET /openapi/device/status".
Published: 2026-05-11T16:02:40.597Z
Updated: 2026-05-11T18:18:25.334Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.