CVE-2025-4043: Milesight UG65-868M-EA Improper Access Control for Volatile Memory Containing Boot Code

Published May 7, 2025
·
Updated

An admin user can gain unauthorized write access to the /etc/rc.local file on the device, which is executed on a system boot.

Affected Software

4 affected components
: Milesight UG65-868M-EA: Firmware versions prior to 60.0.0.46
Milesight UG65-868M-EA
All of the following
Milesight Ug65-868m-ea Firmware<60.0.0.46
Milesight UG65-868M-EA

Remediation

Information

Milesight released the latest firmware Version 60.0.0.46 for the UG65 gateway. Users can download the latest firmware from the Milesight download center. https://www.milesight.com/iot/resources/download-center/#firmware-ug65 Please contact Milesight technical support https://www.milesight.com/company/contactus for more information about this issue and for instructions for installing the latest firmware.

Event History

May 7, 2025
CVE Published
via MITRE·08:25 PM
Data Sourced
via MITRE·08:25 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-4043?

CVE-2025-4043 has a high severity rating due to the potential for unauthorized write access to critical system files.

2

How do I fix CVE-2025-4043?

To fix CVE-2025-4043, update the Milesight UG65-868M-EA firmware to version 60.0.0.46 or later.

3

What risks are associated with CVE-2025-4043?

CVE-2025-4043 allows an admin user to modify the /etc/rc.local file, which could lead to unauthorized code execution at system boot.

4

How can I verify if my device is affected by CVE-2025-4043?

Check if your Milesight UG65-868M-EA device is running a firmware version prior to 60.0.0.46 to determine if it is affected.

5

Is there a workaround for CVE-2025-4043 if I can't update my firmware?

A temporary workaround for CVE-2025-4043 could involve restricting access to admin accounts or monitoring changes to the /etc/rc.local file until the firmware can be updated.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203