CVE-2024-32211 is a vulnerability identified in LOGINT LoMag Inventory Management software versions 1.0.20.120 and earlier. The flaw resides in the UserClass.cs and Settings.cs components, which handle user-related and configuration data. The vulnerability allows a local attacker with low privileges to access sensitive information that should otherwise be protected. According to the CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), the attack requires local access and low complexity, with no user interaction needed. The attacker does not need elevated privileges but must have some level of authenticated access to the system. The impact is limited to confidentiality, with no effect on integrity or availability. The weakness is categorized under CWE-922, which relates to improper restriction of operations within the bounds of a memory buffer or similar resource, leading to information disclosure. No patches or exploit code are currently publicly available, but the vulnerability is officially published and should be addressed promptly by affected organizations.

The primary impact of this vulnerability is unauthorized disclosure of sensitive information, which could include user credentials, configuration settings, or other critical data managed by the UserClass.cs and Settings.cs components. Such information leakage can facilitate further attacks, including privilege escalation or lateral movement within the network. Since the vulnerability requires local access with low privileges, the risk is higher in environments where multiple users share systems or where attackers can gain initial footholds with limited rights. The confidentiality breach could lead to compliance violations, loss of customer trust, and potential financial or operational damage depending on the sensitivity of the exposed data. However, the lack of impact on integrity and availability reduces the risk of direct system disruption or data manipulation.

Organizations should immediately assess their use of LOGINT LoMag Inventory Management software and identify any instances running version 1.0.20.120 or earlier. Since no official patches are currently available, mitigation should focus on restricting local access to trusted users only and implementing strict access controls to limit the ability of low-privilege users to access sensitive components. Monitoring and auditing local user activities can help detect suspicious attempts to access UserClass.cs and Settings.cs files. Network segmentation and endpoint protection can reduce the risk of attackers gaining local access. Additionally, organizations should engage with the vendor for updates or patches and apply them promptly once released. Employing application whitelisting and least privilege principles will further reduce the attack surface.