Cyber Resilience

CVE-2024-0939

Byzoro Smart S210 Firmware ≤ 2024-01-17

Public PoC
Published
26 January 2024
Modified
21 November 2024
CVSS Score v3.1 6.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
EPSS Score 0.44 99th percentile
Risk Priority 75 floored blend · peak EPSS

Summary

CVE-2024-0939 is a medium-severity Unrestricted Upload of File with Dangerous Type (CWE-434) vulnerability in Byzoro Smart S210 Firmware. Its CVSS base score is 6.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 1% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SI-3 (Malicious Code Protection) and CM-7 (Least Functionality) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

A vulnerability classified under CWE-434 has been identified in the Byzoro Smart S210 Management Platform up to version 20240117. It resides in the unknown code of the file /Tool/uploadfile.php, where manipulation of the file_upload argument permits unrestricted file uploads. The issue carries a CVSS 3.1 score of 6.3 and was publicly disclosed under VDB-252184 after the vendor failed to respond to early notification.

Remote attackers who possess low-privileged credentials can initiate the attack over the network without user interaction. Successful exploitation allows upload of arbitrary files, which can result in limited impacts to confidentiality, integrity, and availability on the affected management platform.

Public references, including detailed exploit descriptions on GitHub and Vuldb entries, contain no information on official patches or mitigations, consistent with the vendor's lack of response. The associated EPSS score has reached a peak of 0.8887 with a current value of 0.8752, indicating sustained exploitation interest following disclosure.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A vulnerability has been found in Byzoro Smart S210 Management Platform up to 20240117 and classified as critical. This vulnerability affects unknown code of the file /Tool/uploadfile.php. The manipulation of the argument file_upload leads to unrestricted upload. The attack can…

more

be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-252184. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1505 Server Software Component Persistence
Adversaries may abuse legitimate extensible development features of servers to establish persistent access to systems.
T1505.003 Web Shell Persistence
Adversaries may backdoor web servers with web shells to establish persistent access to systems.
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
T1105 Ingress Tool Transfer Command And Control
Adversaries may transfer tools or other files from an external system into a compromised environment.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-6576Same product: Byzoro Smart S210
CVE-2023-6575Same product: Byzoro Smart S210
CVE-2023-7039Same product: Byzoro Smart S210
CVE-2023-5489Same vendor: Byzoro
CVE-2023-5488Same vendor: Byzoro
CVE-2023-5490Same vendor: Byzoro
CVE-2023-5491Same vendor: Byzoro
CVE-2023-5493Same vendor: Byzoro
CVE-2023-6274Same vendor: Byzoro
CVE-2024-1918Same vendor: Byzoro

Affected Assets

byzoro
smart s210 firmware
≤ 2024-01-17

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V5.1.1

Mitigating Controls (NIST 800-53 r5) AI

Malicious-code protection at entry points blocks dangerous file types from being accepted and executed.

Least functionality restricts the file types and automatic processing capabilities the system will accept.

SC-18 Mobile Code partial match

Mobile-code controls define, authorize, and block unacceptable uploaded code before automatic processing occurs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-05 mostly match
prevents

Restricting execution of unauthorized software directly blocks dangerous uploaded files from running.

PR.PS-01 partial match
prevents

Hardened configuration baselines can enforce allowed file types and processing rules.

PR.PS-06 partial match
prevents

Secure development practices include input validation and file-type restrictions that prevent this weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Configuration and acceptance testing verify that file-upload handling enforces allowed types and does not permit dangerous content to be stored or executed.

prevents

Secure-coding guidelines and security testing explicitly address restrictions on allowed file types and upload handling, reducing the risk that dangerous file uploads are accepted without validation.

prevents

Mandated testing for malicious content and known vulnerabilities reduces the likelihood that an outsourced component will contain or accept dangerous file types that could later be uploaded or executed.

mitigates

Application allow-listing and pre-use scanning of received files directly blocks the introduction of executable content that has not been vetted, eliminating the primary vector for unrestricted dangerous file uploads.

References