# CVE-2022-38546: Misconfiguration in NBG7510 firmware

> An unauthenticated attacker can access the DNS server in AP mode due to a misconfiguration, potentially exposing sensitive data or bypassing security controls.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Dec 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-pmr6-wh49-g8wf

## What is CVE-2022-38546?

CVE-2022-38546 is a medium-severity vulnerability in Zyxel NBG7510 firmware, published on 21 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A DNS misconfiguration was found in Zyxel NBG7510 firmware versions prior to V1.00(ABZY.3)C0, which could allow an unauthenticated attacker to access the DNS server when the device is switched to the AP mode.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Zyxel Nbg7510 Firmware.

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

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

## Is CVE-2022-38546 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-38546 is a medium-severity vulnerability in Zyxel NBG7510 firmware, published on 21 Dec 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-2022-38546 in the wild and no public exploit code.

Affected product: Zyxel NBG7510 firmware. 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-38546/ (Markdown: https://insights.sbomify.com/CVE-2022-38546/index.md)
```

## Sources

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

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