VulnerabilityPublished 4 Dec 2023Updated 29 May 2025

CVE-2023-42716: Unisoc (Shanghai) Technologies SC7731E/SC9832E/SC9863A/T310/T606/T612/T616/T610/T618/T760/T770/T820/S8000 · Resource Exposure

Affects Unisoc (Shanghai) Technologies SC7731E/SC9832E/SC9863A/T310/T606/T612/T616/T610/T618/T760/T770/T820/S8000Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Dec 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Given the absence of publicly available patches, European organizations should implement several targeted mitigations: 1) Inventory and identify devices using affected Unisoc chipsets running Android 11 or 12 to assess exposure. 2) Restrict network access to telephony services where possible, such as limiting untrusted network traffic or employing network segmentation to reduce attack surface. 3) Employ mobile device management (MDM) solutions to enforce strict security policies, including disabling unnecessary telephony features or services if feasible. 4) Monitor network traffic for unusual patterns indicative of exploitation attempts targeting telephony services. 5) Engage with device vendors and Unisoc for timely updates and patches, and prioritize patch deployment once available. 6) Educate users about the risks and encourage cautious behavior regarding network connections, especially on untrusted Wi-Fi or cellular networks. 7) Consider deploying endpoint detection and response (EDR) tools capable of identifying anomalous telephony service behavior. These steps go beyond generic advice by focusing on device-specific inventory, network-level controls, and proactive monitoring tailored to the nature of this vulnerability.

Description

In telephony service, there is a possible missing permission check. This could lead to remote information disclosure no additional execution privileges needed

Impact

For European organizations, the impact of this vulnerability could be substantial, particularly for enterprises and government agencies that rely on mobile devices using Unisoc chipsets for communication. Unauthorized disclosure of telephony information could lead to privacy breaches, exposure of call metadata, subscriber identity information, or other sensitive telephony-related data. This could facilitate targeted phishing, social engineering, or surveillance activities against employees, potentially compromising organizational security. Additionally, sectors such as finance, healthcare, and critical infrastructure that depend on secure mobile communications could face increased risks of data leakage or espionage. The vulnerability's remote exploitability without authentication or user interaction heightens the threat level, as attackers could leverage network access to compromise devices silently. Although the vulnerability does not impact integrity or availability directly, the confidentiality breach alone can have cascading effects on trust, compliance with data protection regulations like GDPR, and overall operational security.

CWE-668Exposure of Resource to Wrong Sphere (opens in a new tab)
Class weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
OWASP Cheat Sheets
Authorization (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

unisoc.com/en_us/secy/announcementDetail/https://www.unisoc.com/en_us/secy/announcementDetail/1731138365803266049 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 8 Jul 2025, 02:26 UTC

WeaknessesCWE-668

Technical details

References

Community reviews

Related threats