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

> An attacker can log in as another user without a password due to incorrect access control in Glewlwyd.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2021-45379, GHSA-9hmj-m2q2-x92g, UBUNTU-CVE-2021-45379

## What is CVE-2021-45379?

CVE-2021-45379 is a high-severity authentication bypass vulnerability in n/a, published on 30 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Glewlwyd 2.0.0, fixed in 2.6.1 is affected by an incorrect access control vulnerability. One user can attempt to log in as another user without its password.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Glewlwyd Project Glewlwyd.

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

Upgrade to a fixed version.

## Is CVE-2021-45379 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-29967](https://insights.sbomify.com/CVE-2022-29967/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-45379 is a high-severity authentication bypass vulnerability in n/a, published on 30 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-45379 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-45379/ (Markdown: https://insights.sbomify.com/CVE-2021-45379/index.md)
```

## Sources

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

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