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

> Unauthenticated attackers can execute arbitrary code on TP-Link Archer A54 routers via a stack overflow vulnerability.

- **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:** 22 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-9cg4-jqq9-fpw7

## What is CVE-2022-25072?

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

### Official description

TP-Link Archer A54 Archer A54(US)_V1_210111 routers were discovered to contain a stack overflow in the function DM_ Fillobjbystr(). This vulnerability allows unauthenticated attackers to execute arbitrary code.

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

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

It affects 1 product.


Products: Tp-Link Archer A54 Firmware.

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

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

## Is CVE-2022-25072 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-44448](https://insights.sbomify.com/CVE-2023-44448/): TP-Link Archer A54 libcmm.so dm_fillObjByStr Stack-based Buffer Overflow Remote Code Execution Vulnerability (medium 6.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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