VulnerabilityPublished 25 Jun 2024Updated 7 Nov 2024

CVE-2024-21739: Geehy APM32F103CCT6, APM32F103RCT6, APM32F103RCT7, and APM32F103VCT6 devices have Incorrect Access

Source CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

5.3Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% 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:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
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: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 25 Jun 2024
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 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

1. Monitor Geehy Semiconductor’s official channels for firmware updates or patches addressing CVE-2024-21739 and apply them promptly once available. 2. Implement network segmentation and strict access controls to limit exposure of devices using affected microcontrollers to untrusted networks. 3. Employ intrusion detection and anomaly monitoring systems to identify unusual device behavior indicative of integrity compromise. 4. Where possible, use secure boot and firmware validation mechanisms to prevent unauthorized firmware modifications. 5. Conduct thorough security audits of embedded systems incorporating these microcontrollers to identify and mitigate potential exploitation vectors. 6. For new designs, consider alternative microcontrollers with robust access control mechanisms and proven security track records. 7. Educate operational technology (OT) and IoT security teams about the vulnerability to ensure rapid response and containment if exploitation attempts are detected.

Description

Geehy APM32F103CCT6, APM32F103RCT6, APM32F103RCT7, and APM32F103VCT6 devices have Incorrect Access Control.

Impact

The primary impact of CVE-2024-21739 is the potential unauthorized modification of device integrity, which can lead to altered or malicious behavior of embedded systems using the affected Geehy microcontrollers. This could result in compromised operational reliability, safety hazards in industrial control environments, and potential cascading failures in IoT ecosystems. Since these microcontrollers are embedded in a wide range of devices globally, the vulnerability poses a risk to manufacturers, industrial operators, and end-users relying on these platforms. The lack of authentication and user interaction requirements lowers the barrier for exploitation, increasing the threat surface. However, the absence of confidentiality and availability impacts limits the scope to integrity-related concerns. Organizations could face increased maintenance costs, downtime, and potential safety incidents if the vulnerability is exploited. The threat is particularly relevant for sectors such as manufacturing, automotive, smart home devices, and critical infrastructure where these microcontrollers are prevalent.

References

tches.iacr.org/index.php/TCHES/article/view/11422/10927 (opens in a new tab)

Community reviews

Loading reviews…