# CVE-2021-28858: Information disclosure in n/a

> An attacker on the local network can intercept sensitive data, including cookies, because the device does not use SSL by default.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-q9w3-4qx4-v262

## What is CVE-2021-28858?

CVE-2021-28858 is a medium-severity vulnerability in n/a, published on 15 Jun 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

TP-Link's TL-WPA4220 4.0.2 Build 20180308 Rel.37064 does not use SSL by default. Attacker on the local network can monitor traffic and capture the cookie and other sensitive information.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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

It affects 1 product.


Products: Tp-Link Tl-Wpa4220 Firmware.

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

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

## Is CVE-2021-28858 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-24297](https://insights.sbomify.com/CVE-2020-24297/): Command injection in n/a (high 8.8)
- [CVE-2021-28857](https://insights.sbomify.com/CVE-2021-28857/): Information disclosure in n/a (high 7.5)
- [CVE-2020-28005](https://insights.sbomify.com/CVE-2020-28005/): Memory corruption in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-28858 is a medium-severity vulnerability in n/a, published on 15 Jun 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-28858 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-28858/ (Markdown: https://insights.sbomify.com/CVE-2021-28858/index.md)
```

## Sources

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

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