O+ Connect's lack of authentication for IPC channels led to a local privilege escalation vulnerability.
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| OPPO | O+ Connect | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Oppo | O+ Connect |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.122% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Oppo
Oppo o+ Connect |
|
| Vendors & Products |
Oppo
Oppo o+ Connect |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Because O+ Connect's IPC service does not authenticate clients, external applications can escalate privileges and perform sensitive actions through the IPC channel. | |
| Title | O+ Connect's lack of authentication for IPC channels led to a local privilege escalation vulnerability. | |
| Weaknesses | CWE-266 | |
| References |
| |
| Metrics |
cvssV3_1
|