# CVE-2024-32211: Information disclosure in n/a

> A local attacker can obtain sensitive information from LOGINT LoMag Inventory Management via vulnerable components.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 May 2024
- **Updated:** 5 Nov 2024
- **Also known as:** GHSA-58qf-7xxx-pw82

## What is CVE-2024-32211?

CVE-2024-32211 is a medium-severity vulnerability in n/a, published on 1 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in LOGINT LoMag Inventory Management v1.0.20.120 and before allows a local attacker to obtain sensitive information via the UserClass.cs and Settings.cs components.

Weakness: CWE-922 (Insecure Storage of Sensitive Information)

## Which versions are affected by CVE-2024-32211?

It affects 1 product.


Products: Logint Lomag Warehouse Management.

## How do I fix CVE-2024-32211?

No fix has been published for CVE-2024-32211 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-32211 being exploited?

There is no known exploitation of CVE-2024-32211 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2024-32212](https://insights.sbomify.com/CVE-2024-32212/): SQL injection in n/a (high 8.1)
- [CVE-2024-32210](https://insights.sbomify.com/CVE-2024-32210/): Hardcoded credentials in n/a (medium 5.3)
- [CVE-2024-32213](https://insights.sbomify.com/CVE-2024-32213/): Hardcoded credentials in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-32211 and fix it if it is affected.

What it is: CVE-2024-32211 is a medium-severity vulnerability in n/a, published on 1 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-32211 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-32211/ (Markdown: https://insights.sbomify.com/CVE-2024-32211/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-32211
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-32211
- OSV: https://osv.dev/vulnerability/CVE-2024-32211

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-32211/
Summaries are generated and may contain mistakes; the official description above is the record.