Skip to main content
CVE-2024-48406VulnerabilityPublished Updated

CVE-2024-48406: umicat · n/a

Affects umicatSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in 0.3.3 : patch umicat as a priority.

Data as of 26 Oct 2026, 06:26 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Nov 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
GitHubsunbk201/umicatpkg:github/sunbk201/umicatOther threatsAffected
  • <=0.3.2
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-48406, organizations should immediately upgrade SunBK201 umicat to version 0.3.3 or later, where the vulnerability has been fixed. If upgrading is not immediately feasible, applying virtual patching or network-level protections such as firewall rules to restrict access to the vulnerable service can reduce exposure. Conduct thorough code reviews and static analysis on custom or integrated components that use the power function or similar logic to identify and remediate buffer overflow risks. Employ runtime protections such as Address Space Layout Randomization (ASLR), Data Execution Prevention (DEP), and stack canaries to make exploitation more difficult. Monitor network traffic and system logs for unusual activity indicative of exploitation attempts. Maintain an incident response plan ready to address potential breaches stemming from this vulnerability. Engage with the software vendor or community to confirm patch availability and verify integrity of updates before deployment.

Description

Buffer Overflow vulnerability in SunBK201 umicat through v.0.3.2 and fixed in v.0.3.3 allows an attacker to execute arbitrary code via the power(uct_int_t x, uct_int_t n) in src/uct_upstream.c.

References

Community reviews

Loading reviews…