LNL-X2210: Buffer Copy without Checking Size of Input
CVE-2022-31481 is a critical-severity buffer copy without checking size of input vulnerability in LNL-X2210 from LenelS2, with a CVSS 3.1 base score of 10.0 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 1.302 as the first without the flaw, so updating LNL-X2210 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.64% chance of exploitation within 30 days, higher than 77% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update LNL-X2210 to 1.302 or a later version.
- Update LNL-X2220 to 1.302 or a later version.
- Update LNL-X3300 to 1.302 or a later version.
- Read the advisory on corporate.carrier.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| LenelS2 | LNL-X2210 | ALL up to, but not including, 1.302 | 1.302 |
| LenelS2 | LNL-X2220 | ALL up to, but not including, 1.302 | 1.302 |
| LenelS2 | LNL-X3300 | ALL up to, but not including, 1.302 | 1.302 |
| LenelS2 | LNL-X4420 | ALL up to, but not including, 1.302 | 1.302 |
| LenelS2 | LNL-4420 | ALL up to, but not including, 1.296 | 1.296 |
| LenelS2 | S2-LP-1501 | ALL up to, but not including, 1.302 | 1.302 |
| LenelS2 | S2-LP-1502 | ALL up to, but not including, 1.302 | 1.302 |
| LenelS2 | S2-LP-2500 | ALL up to, but not including, 1.302 | 1.302 |
| LenelS2 | S2-LP-4502 | ALL up to, but not including, 1.302 | 1.302 |
| HID Mercury | LP1501 | ALL up to, but not including, 1.302 | 1.302 |
| HID Mercury | LP1502 | ALL up to, but not including, 1.302 | 1.302 |
| HID Mercury | LP2500 | ALL up to, but not including, 1.302 | 1.302 |
| HID Mercury | LP4502 | ALL up to, but not including, 1.302 | 1.302 |
| HID Mercury | EP4502 | ALL up to, but not including, 1.296 | 1.296 |
| Hidglobal | Lp1501 Firmware | before 1.302 | 1.302 |
| Hidglobal | Lp1502 Firmware | before 1.302 | 1.302 |
| Hidglobal | Lp2500 Firmware | before 1.302 | 1.302 |
| Hidglobal | Lp4502 Firmware | before 1.302 | 1.302 |
| Hidglobal | Ep4502 Firmware | before 1.296 | 1.296 |
| Carrier | Lenels2 Lnl-4420 Firmware | before 1.296 | 1.296 |
| Carrier | Lenels2 Lnl-x2210 Firmware | before 1.302 | 1.302 |
| Carrier | Lenels2 Lnl-x2220 Firmware | before 1.302 | 1.302 |
| Carrier | Lenels2 Lnl-x3300 Firmware | before 1.302 | 1.302 |
| Carrier | Lenels2 Lnl-x4420 Firmware | before 1.302 | 1.302 |
| Carrier | Lenels2 S2-lp-1501 Firmware | before 1.302 | 1.302 |
Version data comes from the organisation that assigned the CVE; 3 further products are omitted here. 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
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- 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:N/UI:N/S:C/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 10.0 | Critical | CNA (carrier.com) |
| CVSS 3.1 | 10.0 | Critical | NVD |
| CVSS 2.0 | 7.5 | High | NVD |
Official description
An unauthenticated attacker can send a specially crafted update file to the device that can overflow a buffer. This vulnerability impacts products based on HID Mercury Intelligent Controllers LP1501, LP1502, LP2500, LP4502, and EP4502 which contain firmware versions prior to 1.302 for the LP series and 1.296 for the EP series. The overflowed data can allow the attacker to manipulate the “normal” code execution to that of their choosing. An attacker with this level of access on the device can monitor all communications sent to and from this device, modify onboard relays, change configuration files, or cause the device to become unstable.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Buffer Copy without Checking Size of Input
The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.
How developers prevent this class of flaw
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
- 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.
More Buffer Copy without Checking Size of Input vulnerabilities (CWE-120)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in LNL-X2210
- 8.8 High severity
- 7.5 High severity
- 8.8 High severity
- 7.5 High severity
- 7.5 High severity
- 9.8 Critical severity
Recent Buffer Copy without Checking Size of Input vulnerabilities
- 9.8 Critical severity
- 7.8 High severity
- 7.5 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.