# CVE-2023-3632: Hard-coded Cryptographic Key in Kunduz - Homework Helper App

> Attackers can bypass authentication and take over accounts in the Kunduz Homework Helper App due to a hard-coded cryptographic key.

- **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:** 9 Aug 2023
- **Updated:** 21 May 2026
- **Also known as:** GHSA-5x8q-jj28-qg7w

## What is CVE-2023-3632?

CVE-2023-3632 is a critical vulnerability in Sifir Bes Education and Informatics Kunduz - Homework Helper App, published on 9 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Use of Hard-coded Cryptographic Key vulnerability in Sifir Bes Education and Informatics Kunduz - Homework Helper App allows Authentication Abuse, Authentication Bypass.

This issue affects Kunduz - Homework Helper App: before 6.2.3.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2023-3632?

It affects 1 product.


Products: Kunduz Kunduz.

## How do I fix CVE-2023-3632?

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

## Is CVE-2023-3632 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-3632 and fix it if it is affected.

What it is: CVE-2023-3632 is a critical vulnerability in Sifir Bes Education and Informatics Kunduz - Homework Helper App, published on 9 Aug 2023. 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-2023-3632 in the wild and no public exploit code.

Affected product: Sifir Bes Education and Informatics Kunduz - Homework Helper App. 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-2023-3632/ (Markdown: https://insights.sbomify.com/CVE-2023-3632/index.md)
```

## Sources

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

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