# CVE-2024-38468: Auth bypass in n/a

> Attackers can reset user passwords without authorization via the resetPassword API, leading to account takeover.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jun 2024
- **Updated:** 26 Mar 2025
- **Also known as:** GHSA-3chh-q8fx-pc2w

## What is CVE-2024-38468?

CVE-2024-38468 is a critical authentication bypass vulnerability in n/a, published on 16 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Shenzhen Guoxin Synthesis image system before 8.3.0 allows unauthorized password resets via the resetPassword API.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

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

It affects 1 product.


Products: Guoxinled Synthesis Image System.

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

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

## Is CVE-2024-38468 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-38466](https://insights.sbomify.com/CVE-2024-38466/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2024-38467](https://insights.sbomify.com/CVE-2024-38467/): Information disclosure in n/a (high 7.5)
- [CVE-2024-38465](https://insights.sbomify.com/CVE-2024-38465/): Information disclosure in n/a (medium 4.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-38468 is a critical authentication bypass vulnerability in n/a, published on 16 Jun 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-38468 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-38468/ (Markdown: https://insights.sbomify.com/CVE-2024-38468/index.md)
```

## Sources

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

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