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

> Remote attackers can read wireless credentials from the HTML source code of Intelbras routers, potentially leading to unauthorized network access.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 14 Apr 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-vvf7-v2jp-v5fv

## What is CVE-2021-3017?

CVE-2021-3017 is a high-severity vulnerability in n/a, published on 14 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The web interface on Intelbras WIN 300 and WRN 342 devices through 2021-01-04 allows remote attackers to discover credentials by reading the def_wirelesspassword line in the HTML source code.

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

It affects 2 products.


Products: Intelbras Win 300 Firmware, Intelbras Wrn 342 Firmware.

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

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

## Is CVE-2021-3017 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-3017 exists.

Public exploit code:

- Intelbras WIN 300/WRN 342 - Credentials Disclosure (nuclei): http/cves/2021/CVE-2021-3017.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2021-3017 is a high-severity vulnerability in n/a, published on 14 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-3017 exists.

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-3017/ (Markdown: https://insights.sbomify.com/CVE-2021-3017/index.md)
```

## Sources

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

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