# CVE-2022-34046: Information disclosure in n/a

> Attackers can retrieve router credentials by viewing the source of a specific administrative page, leading to unauthorized 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:** 20 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-jr5r-25mv-wfhm

## What is CVE-2022-34046?

CVE-2022-34046 is a high-severity vulnerability in n/a, published on 20 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An access control issue in Wavlink WN533A8 M33A8.V5030.190716 allows attackers to obtain usernames and passwords via view-source:http://IP_ADDRESS/sysinit.shtml?r=52300 and searching for [logincheck(user);].

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2022-34046?

It affects 1 product.


Products: Wavlink Wn533a8 Firmware.

## How do I fix CVE-2022-34046?

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

## Is CVE-2022-34046 being exploited?

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

Public exploit code:

- Wavlink WN533A8 - Password Disclosure (exploitdb)
- WAVLINK WN533A8 - Improper Access Control (nuclei): http/cves/2022/CVE-2022-34046.yaml

## Other vulnerabilities in n/a

- [CVE-2022-34048](https://insights.sbomify.com/CVE-2022-34048/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-34046 and fix it if it is affected.

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

## Sources

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

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