# CVE-2022-34020: Cross-site request forgery in n/a

> Attackers can exploit CSRF to add admin users to the ResIOT IoT Platform, leading to privilege escalation and account takeover.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Oct 2022
- **Updated:** 16 May 2025
- **Also known as:** GHSA-xqqf-j87h-83gq

## What is CVE-2022-34020?

CVE-2022-34020 is a high-severity vulnerability in n/a, published on 13 Oct 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross Site Request Forgery (CSRF) vulnerability in ResIOT ResIOT IOT Platform + LoRaWAN Network Server through 4.1.1000114 allows attackers to add new admin users to the platform or other unspecified impacts.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Resiot Iot Platform and Lorawan Network Server.

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

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

## Is CVE-2022-34020 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-34022](https://insights.sbomify.com/CVE-2022-34022/): SQL injection in n/a (high 7.2)
- [CVE-2022-34021](https://insights.sbomify.com/CVE-2022-34021/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-34020 is a high-severity vulnerability in n/a, published on 13 Oct 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-34020 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-34020/ (Markdown: https://insights.sbomify.com/CVE-2022-34020/index.md)
```

## Sources

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

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