# CVE-2019-6967: Cross-site request forgery in n/a

> Cross-site request forgery in AirTies Air5341 routers allows attackers to perform unauthorized actions on behalf of authenticated users.

- **Severity:** High 8.8 (`CVSS:3.0/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:** 17 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-82v8-7rmr-rgrh

## What is CVE-2019-6967?

CVE-2019-6967 is a high-severity vulnerability in n/a, published on 17 Mar 2019. 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

AirTies Air5341 1.0.0.12 devices allow cgi-bin/login CSRF.

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

## Which versions are affected by CVE-2019-6967?

It affects 1 product.


Products: Airties Air 5341 Firmware.

## How do I fix CVE-2019-6967?

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

## Is CVE-2019-6967 being exploited?

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

Public exploit code:

- AirTies Air5341 Modem 1.0.0.12 - Cross-Site Request Forgery (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-6967 and fix it if it is affected.

What it is: CVE-2019-6967 is a high-severity vulnerability in n/a, published on 17 Mar 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-6967 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-2019-6967/ (Markdown: https://insights.sbomify.com/CVE-2019-6967/index.md)
```

## Sources

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

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