Skip to main content
VulnerabilityPublished Updated

CVE-2024-39343: Input · Improper Validation of Specified Quantity

Source CVE Database V5

0

Not known to be exploited · CVSS 7.0 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
7.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AC:H/AV:N/A:H/C:L/I:L/PR:N/S:U/UI:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Dec 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

AI-suggested

  1. Monitor Samsung and device vendors for official firmware or baseband software updates addressing CVE-2024-39343 and apply patches promptly once available.
  2. Employ network-level protections such as filtering and anomaly detection on cellular signaling traffic to identify and block malformed MM messages that could trigger the vulnerability.
  3. Coordinate with mobile network operators to implement safeguards against malicious signaling messages at the network infrastructure level.
  4. For enterprise deployments, consider using mobile device management (MDM) solutions to enforce timely updates and monitor device connectivity issues.
  5. Educate users and administrators about potential connectivity disruptions and establish contingency communication plans.
  6. Where possible, isolate critical devices from untrusted cellular networks or use VPNs and secure communication channels to reduce exposure.
  7. Conduct regular security assessments on mobile devices and IoT endpoints using affected processors to detect anomalous behavior indicative of exploitation attempts.
  8. Maintain up-to-date inventories of devices with affected Exynos processors to prioritize patching and risk management efforts.

Description

An issue was discovered in Samsung Mobile Processor and Wearable Processor Exynos 2100, 1280, 2200, 1330, 1380, 1480, 2400, 9110, Modem 5123, and Modem 5300. The baseband software does not properly check the length specified by the MM (Mobility Management) module, which can lead to Denial of Service.

References

Community reviews

Loading reviews…