# CVE-2018-18466: Information disclosure in n/a

> An attacker with local access can read emergency credentials from debug logs if the application is configured in debug mode.

- **Severity:** High 7.0 (`CVSS:3.0/AV:L/AC:H/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:** 18 Mar 2019
- **Updated:** 30 May 2025
- **Also known as:** GHSA-8wpj-w799-92rg

## What is CVE-2018-18466?

CVE-2018-18466 is a high-severity vulnerability in n/a, published on 18 Mar 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 in SecurEnvoy SecurAccess 9.3.502. When put in Debug mode and used for RDP connections, the application stores the emergency credentials in cleartext in the logs (present in the DEBUG folder) that can be accessed by anyone. NOTE: The vendor disputes this as a vulnerability since the disclosure of a local account password (actually an alpha numeric passcode) is achievable only when a custom registry key is added to the windows registry. This action requires administrator access and the registry key is only provided by support staff at securenvoy to troubleshoot customer issues.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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

It affects 1 product.


Products: Securenvoy Securaccess.

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

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

## Is CVE-2018-18466 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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