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

> Attackers can bypass captive portal authentication by setting authType to 0, gaining unauthorized access to the protected network.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** 7 Mar 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-v5jw-8pjp-rgfp

## What is CVE-2021-44032?

CVE-2021-44032 is a high-severity authentication bypass vulnerability in n/a, published on 7 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TP-Link Omada SDN Software Controller before 5.0.15 does not check if the authentication method specified in a connection request is allowed. An attacker can bypass the captive portal authentication process by using the downgraded "no authentication" method, and access the protected network. For example, the attacker can simply set window.authType=0 in client-side JavaScript.

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

It affects 1 product.


Products: Tp-Link Omada Software Controller.

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

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

## Is CVE-2021-44032 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-44032 is a high-severity authentication bypass vulnerability in n/a, published on 7 Mar 2022. 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-44032 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-44032/ (Markdown: https://insights.sbomify.com/CVE-2021-44032/index.md)
```

## Sources

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

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