CVE-2022-31484 — User Account Deletion Unauthenticated

An unauthenticated attacker can send a specially crafted network packet to delete a user from the web interface. This vulnerability impacts products based on HID Mercury Intelligent Controllers LP1501, LP1502, LP2500, LP4502, and EP4502 which contain firmware versions prior to 1.29. The impact of this vulnerability is that an unauthenticated attacker could restrict access to the web interface to legitimate users and potentially requiring them to use the default user dip switch procedure to gain access back.

Published Jun 6, 2022Updated Sep 17, 2024Sources: cvelistV5, Carrier

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

chance of exploitation in 30 days

Affects

lenels2

14 products listed

CVSS base

7.5

HIGH

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (2)

lenels2 hid mercury

Products (14)

lnl x2210lnl x2220lnl x3300lnl x4420lnl 4420s2 lp 1501s2 lp 1502s2 lp 2500s2 lp 4502lp1501lp1502lp2500lp4502ep4502

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
7.5	CVSS 3.1	HIGH	—	—	cvelistV5

Weakness & attack patterns

CWE-425

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

T1083File and Directory Discovery
T1565.002Data Manipulation: Transmitted Data Manipulation

References

1 on the record

www.corporate.carrier.com/product-security/advisories-resources/
x_refsource_MISC

Elsewhere on this site

lenels2every CVE for this vendor
hid mercuryevery CVE for this vendor
CWE-425other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.