# CVE-2022-47040: Privilege escalation in n/a

> Attackers can escalate privileges on ASKEY routers by exploiting a vulnerability involving tcpdump and crafted files in the /tmp directory.

- **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:** 24 Jan 2023
- **Updated:** 2 Apr 2025
- **Also known as:** GHSA-p896-8j6m-mwc6

## What is CVE-2022-47040?

CVE-2022-47040 is a high-severity vulnerability in n/a, published on 24 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in ASKEY router RTF3505VW-N1 BR_SV_g000_R3505VMN1001_s32_7 allows attackers to escalate privileges via running the tcpdump command after placing a crafted file in the /tmp directory and sending crafted packets through port 80.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Askey Rtf3505vw-N1 Firmware.

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

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

## Is CVE-2022-47040 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-47040 is a high-severity vulnerability in n/a, published on 24 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-47040 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-47040/ (Markdown: https://insights.sbomify.com/CVE-2022-47040/index.md)
```

## Sources

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

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