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

> Attackers can bypass domain verification during password resets to take over user accounts in the Linen web application.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 1 Sep 2024
- **Updated:** 3 Sep 2024
- **Also known as:** GHSA-vg84-cxx6-3j79

## What is CVE-2024-45522?

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

### Official description

Linen before cd37c3e does not verify that the domain is linen.dev or www.linen.dev when resetting a password. This occurs in create in apps/web/pages/api/forgot-password/index.ts.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Linen Linen.

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

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

## Is CVE-2024-45522 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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