How severe is CVE-2024-41999?

CVE-2024-41999 has a CVSS 3.x base score of 6.8, rated medium severity. It is exploitable over physical access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2024-41999 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (17th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2024-41999?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2024-41999 have an EU (EUVD) identifier?

Yes. CVE-2024-41999 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-39315.

When was CVE-2024-41999 published?

CVE-2024-41999 was published on 2024-09-30 and last updated on 2026-06-17.

CVE-2024-41999

CVE-2024-41999 is a medium-severity vulnerability with a CVSS 3.x base score of 6.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-489.

Key facts

Severity: Medium (CVSS 3.x base score 6.8)
EPSS exploit prediction: 0% (17th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2024-39315
Weakness: CWE-489
Published: 2024-09-30
Last modified: 2026-06-17

Description

Smart-tab Android app installed April 2023 or earlier contains an active debug code vulnerability. If this vulnerability is exploited, an attacker with physical access to the device may exploit the debug function to gain access to the OS functions, escalate the privilege, change the device's settings, or spoof devices in other rooms.

Frequently asked questions

What is CVE-2024-41999?: Smart-tab Android app installed April 2023 or earlier contains an active debug code vulnerability. If this vulnerability is exploited, an attacker with physical access to the device may exploit the debug function to gain access to the OS functions, escalate the privilege, change the device's settings, or spoof devices in other rooms.
How severe is CVE-2024-41999?: CVE-2024-41999 has a CVSS 3.x base score of 6.8, rated medium severity. It is exploitable over physical access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2024-41999 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (17th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2024-41999?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2024-41999 have an EU (EUVD) identifier?: Yes. CVE-2024-41999 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-39315.
When was CVE-2024-41999 published?: CVE-2024-41999 was published on 2024-09-30 and last updated on 2026-06-17.

References

Other CWE-489 vulnerabilities

CVE-2023-4804 — Critical (CVSS 10.0): An unauthorized user could access debug features in Quantum HD Unity products that were accidentally exposed.
CVE-2026-49188 — Critical (CVSS 9.8): The ai_cmd utility executes with full root permissions. It pipes socket inputs directly to popen(), paving the way…
CVE-2024-46873 — Critical (CVSS 9.8): Multiple SHARP routers leave the hidden debug function enabled. An arbitrary OS command may be executed with the root…
CVE-2024-21785 — Critical (CVSS 9.8): A leftover debug code vulnerability exists in the Telnet Diagnostic Interface functionality of AutomationDirect P3-550E…
CVE-2024-32047 — Critical (CVSS 9.8): Hard-coded credentials for the CyberPower PowerPanel test server can be found in the production code. This might…
CVE-2024-28008 — Critical (CVSS 9.8): Active Debug Code in NEC Corporation Aterm WG1800HP4, WG1200HS3, WG1900HP2, WG1200HP3, WG1800HP3, WG1200HS2, WG1900HP,…

Browse all CWE-489 vulnerabilities →