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

> Attackers can forge JWTs using hardcoded signing keys to bypass authentication and escalate privileges in mall-tiny applications.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 31 Jan 2025
- **Updated:** 13 Mar 2025
- **Also known as:** GHSA-5ggv-wq69-w49q

## What is CVE-2024-57432?

CVE-2024-57432 is a high-severity vulnerability in n/a, published on 31 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

macrozheng mall-tiny 1.0.1 suffers from Insecure Permissions. The application's JWT signing keys are hardcoded and do not change. User information is explicitly written into the JWT and used for subsequent privilege management, making it is possible to forge the JWT of any user to achieve authentication bypass.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Macrozheng Mall-Tiny.

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

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

## Is CVE-2024-57432 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-57432 exists.

## Other vulnerabilities in n/a

- [CVE-2024-57434](https://insights.sbomify.com/CVE-2024-57434/): Auth bypass in n/a (high 8.8)
- [CVE-2024-57433](https://insights.sbomify.com/CVE-2024-57433/): Auth bypass in n/a (high 7.5)
- [CVE-2024-57435](https://insights.sbomify.com/CVE-2024-57435/): Null dereference in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-57432 is a high-severity vulnerability in n/a, published on 31 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-57432 exists.

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-57432/ (Markdown: https://insights.sbomify.com/CVE-2024-57432/index.md)
```

## Sources

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

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