# CVE-2024-32213: Hardcoded credentials in n/a

> The application allows weak, hard-coded passwords by default, enabling attackers to easily guess credentials and take over user accounts.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-2j96-ww2p-cpjq

## What is CVE-2024-32213?

CVE-2024-32213 is a medium-severity vulnerability in n/a, published on 1 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The LoMag WareHouse Management application version 1.0.20.120 and older were found to allow weak passwords. By default, hard-coded passwords of 10 characters with little or no complexity are allowed.

Weakness: CWE-521 (Weak Password Requirements)

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

It affects 1 product.


Products: Logint Lomag Warehouse Management.

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

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

## Is CVE-2024-32213 being exploited?

There is no known exploitation of CVE-2024-32213 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-32211](https://insights.sbomify.com/CVE-2024-32211/): Information disclosure in n/a (medium 5.5)
- [CVE-2024-32210](https://insights.sbomify.com/CVE-2024-32210/): Hardcoded credentials in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-32213 is a medium-severity vulnerability in n/a, published on 1 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-32213 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-32213/ (Markdown: https://insights.sbomify.com/CVE-2024-32213/index.md)
```

## Sources

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

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