# CVE-2022-36507: Memory corruption in n/a

> A stack overflow in the AddWlanMacList function of H3C Magic NX18 Plus routers allows attackers to execute arbitrary code or cause a denial of service.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 25 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-74pj-xh5v-pwfg

## What is CVE-2022-36507?

CVE-2022-36507 is a high-severity memory corruption vulnerability in n/a, published on 25 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

H3C Magic NX18 Plus NX18PV100R003 was discovered to contain a stack overflow via the function AddWlanMacList.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: H3c Magic Nx18 Plus Firmware.

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

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

## Is CVE-2022-36507 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-36489](https://insights.sbomify.com/CVE-2022-36489/): Memory corruption in n/a (high 7.8)
- [CVE-2022-36490](https://insights.sbomify.com/CVE-2022-36490/): Memory corruption in n/a (high 7.8)
- [CVE-2022-36491](https://insights.sbomify.com/CVE-2022-36491/): Memory corruption in n/a (high 7.8)
- [CVE-2022-36492](https://insights.sbomify.com/CVE-2022-36492/): Memory corruption in n/a (high 7.8)
- [CVE-2022-36493](https://insights.sbomify.com/CVE-2022-36493/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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