# CVE-2019-7745: Information disclosure in n/a

> Remote attackers can obtain the Wi-Fi password from JioFi 4 routers by sending a specific CGI request, exposing network credentials.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 7 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-75v7-h9gp-f766

## What is CVE-2019-7745?

CVE-2019-7745 is a critical vulnerability in n/a, published on 7 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

JioFi 4 jmr1140 Amtel_JMR1140_R12.07 devices allow remote attackers to obtain the Wi-Fi password by making a cgi-bin/qcmap_web_cgi Page=GetWiFi_Setting request and then reading the wpa_security_key field.

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

It affects 1 product.


Products: Jio Jmr1140 Firmware.

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

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

## Is CVE-2019-7745 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-7746](https://insights.sbomify.com/CVE-2019-7746/): Cross-site request forgery in n/a (high 8.1)
- [CVE-2019-7687](https://insights.sbomify.com/CVE-2019-7687/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-7745 is a critical vulnerability in n/a, published on 7 May 2019. 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-2019-7745 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-7745/ (Markdown: https://insights.sbomify.com/CVE-2019-7745/index.md)
```

## Sources

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

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