# CVE-2024-3777: Ai3 QbiBot - Broken Access Control

> Unauthenticated attackers can reset any user's password due to missing access controls in the password reset feature.

- **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:** 15 Apr 2024
- **Updated:** 14 Oct 2024
- **Also known as:** GHSA-v8f2-89xw-2297

## What is CVE-2024-3777?

CVE-2024-3777 is a critical authentication bypass vulnerability in Ai3 QbiBot, published on 15 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The password reset feature of Ai3 QbiBot lacks proper access control, allowing unauthenticated remote attackers to reset any user's password.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Ai3 Qbibot.

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

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

## Is CVE-2024-3777 being exploited?

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

## Other vulnerabilities in Ai3 QbiBot

- [CVE-2024-3778](https://insights.sbomify.com/CVE-2024-3778/): Ai3 QbiBot - Unrestricted File Upload (high 7.2)
- [CVE-2024-7204](https://insights.sbomify.com/CVE-2024-7204/): Ai3 QbiBot - Stored XSS (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-3777 is a critical authentication bypass vulnerability in Ai3 QbiBot, published on 15 Apr 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-3777 in the wild and no public exploit code.

Affected product: Ai3 QbiBot. 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-3777/ (Markdown: https://insights.sbomify.com/CVE-2024-3777/index.md)
```

## Sources

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

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