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

> Local attackers can retrieve admin credentials from unencrypted cookies, enabling unauthorized administrative access to the router.

- **Severity:** High 7.8 (`CVSS:3.0/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:** 6 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9m67-qxr7-3jg8

## What is CVE-2019-7311?

CVE-2019-7311 is a high-severity vulnerability in n/a, published on 6 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered on Linksys WRT1900ACS 1.0.3.187766 devices. A lack of encryption in how the user login cookie (admin-auth) is stored on a victim's computer results in the admin password being discoverable by a local attacker, and usable to gain administrative access to the victim's router. The admin password is stored in base64 cleartext in an "admin-auth" cookie. An attacker sniffing the network at the time of login could acquire the router's admin password. Alternatively, gaining physical access to the victim's computer soon after an administrative login could result in compromise.

Weakness: CWE-311 (Missing Encryption of Sensitive Data)

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

It affects 1 product.


Products: Linksys Wrt1900acs Firmware.

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

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

## Is CVE-2019-7311 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-7579](https://insights.sbomify.com/CVE-2019-7579/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-7311 is a high-severity vulnerability in n/a, published on 6 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-7311 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-7311/ (Markdown: https://insights.sbomify.com/CVE-2019-7311/index.md)
```

## Sources

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

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