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

> A buffer overflow in the Linksys E1200 router allows attackers to execute arbitrary code or cause a denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Aug 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-mh8q-jxj8-6jcr

## What is CVE-2022-38555?

CVE-2022-38555 is a critical memory corruption vulnerability in n/a, published on 28 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Linksys E1200 v1.0.04 is vulnerable to Buffer Overflow via ej_get_web_page_name.

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

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

It affects 1 product.


Products: Linksys E1200 Firmware.

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

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

## Is CVE-2022-38555 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-60690](https://insights.sbomify.com/CVE-2025-60690/): Memory corruption in n/a (high 8.8)
- [CVE-2025-60691](https://insights.sbomify.com/CVE-2025-60691/): Memory corruption in n/a (high 8.8)
- [CVE-2025-60692](https://insights.sbomify.com/CVE-2025-60692/): Memory corruption in n/a (high 8.4)
- [CVE-2025-60694](https://insights.sbomify.com/CVE-2025-60694/): Memory corruption in n/a (high 7.5)
- [CVE-2018-3953](https://insights.sbomify.com/CVE-2018-3953/): Command injection in ESeries E1200 (high 7.2)

## Fix prompt for AI coding agents

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

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

## Sources

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

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