2K Indoor Wi-Fi Security Camera: Stack-based Buffer Overflow
CVE-2024-52547 is a high-severity stack-based buffer overflow vulnerability in 2K Indoor Wi-Fi Security Camera from Lorex, with a CVSS 3.1 base score of 7.2 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. The record lists version 2.800.0000000.8.R.20241111 as the first without the flaw, so updating 2K Indoor Wi-Fi Security Camera to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.72% chance of exploitation within 30 days, higher than 54% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update 2K Indoor Wi-Fi Security Camera to 2.800.0000000.8.R.20241111 or a later version.
- Update w461asc-e_firmware to 2.800.0000000.8.r.20241111 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Lorex | 2K Indoor Wi-Fi Security Camera | before 2.800.0000000.8.R.20241111 | 2.800.0000000.8.R.20241111 |
| Lorextechnology | w461asc-e_firmware | before 2.800.0000000.8.r.20241111 | 2.800.0000000.8.r.20241111 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- HighAdministrator-level access is required first.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (rapid7.com).
Official description
An authenticated attacker can trigger a stack based buffer overflow in the DHIP Service (TCP port 80). This vulnerability has been resolved in firmware version 2.800.0000000.8.R.20241111.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Stack-based Buffer Overflow
The product writes past the end of a buffer that was allocated on the stack.
How developers prevent this class of flaw
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
- Use an abstraction library to abstract away risky APIs. Not a complete solution.
- Implement and perform bounds checking on input.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in 2K Indoor Wi-Fi Security Camera
- 7.5 High severity
- 7.5 High severity
- 9.8 Critical severity
Recent Stack-based Buffer Overflow vulnerabilities
- 7.8 High severity
- 8.2 High severity
- 9.0 Critical severity
- 7.5 High severity
- 7.7 High severity
- 8.8 High severity
Spotted an error? Tell us.