# CVE-2018-5797: Hardcoded credentials in n/a

> An attacker with wired port access can decrypt packets using a hardcoded AES key to obtain cleartext credentials.

- **Severity:** High 7.5 (`CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3jvr-3w2h-527p

## What is CVE-2018-5797?

CVE-2018-5797 is a high-severity vulnerability in n/a, published on 5 Feb 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in Extreme Networks ExtremeWireless WiNG 5.x before 5.8.6.9 and 5.9.x before 5.9.1.3. There is an Smint_encrypt Hardcoded AES Key that can be used for packet decryption (obtaining cleartext credentials) by an attacker who has access to a wired port.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2018-5797?

It affects 1 product.


Products: Extremenetworks Extremewireless Wing.

## How do I fix CVE-2018-5797?

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

## Is CVE-2018-5797 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-5787](https://insights.sbomify.com/CVE-2018-5787/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-5797 and fix it if it is affected.

What it is: CVE-2018-5797 is a high-severity vulnerability in n/a, published on 5 Feb 2018. 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-2018-5797 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-2018-5797/ (Markdown: https://insights.sbomify.com/CVE-2018-5797/index.md)
```

## Sources

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

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