Persistent code execution via unauthorized rc.local writes
Published May 7, 2025 · Updated May 8, 2025
Improper access control in Milesight UG65 firmware before 60.0.0.46 allows remote authenticated users to modify a boot-time script. The affected administrative interface permits writes to /etc/rc.local, whose contents the device executes during system boot. Administrative credentials and a reboot are required for modified commands to run, enabling persistent system-level code execution.
Summary
What happened
Improper access control in Milesight UG65 firmware before 60.0.0.46 allows remote authenticated users to modify a boot-time script. The affected administrative interface permits writes to /etc/rc.local, whose contents the device executes during system boot. Administrative credentials and a reboot are required for modified commands to run, enabling persistent system-level code execution.
The record
- CVE
- CVE-2025-4043
- Published
- May 7, 2025
- Updated
- May 8, 2025
- Vendor
- Milesight
- Product
- UG65
- Classifications
- CWE-1274, T1037.004
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- May 7, 2025CVE publishedPublication date reported by the CVE source.
- May 8, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <60.0.0.46
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo