# CVE-2021-28293: Auth bypass in n/a

> Unauthenticated attackers can take over any user account by exploiting a misconfigured password reset feature in Seceon aiSIEM.

- **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:** 8 Jun 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-xqx5-9rjr-cjq9

## What is CVE-2021-28293?

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

### Official description

Seceon aiSIEM before 6.3.2 (build 585) is prone to an unauthenticated account takeover vulnerability in the Forgot Password feature. The lack of correct configuration leads to recovery of the password reset link generated via the password reset functionality, and thus an unauthenticated attacker can set an arbitrary password for any user.

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

## Which versions are affected by CVE-2021-28293?

It affects 1 product.


Products: Seceon Aisiem.

## How do I fix CVE-2021-28293?

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

## Is CVE-2021-28293 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-28293 and fix it if it is affected.

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

## Sources

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

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