dbcve.org
SecuraccessApplication · Securenvoy

CVE-2018-18466

HIGH · 7.0 CVSS v3.0 Published 2019-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SecurEnvoy SecurAccess 9.3.502 stores emergency credentials in cleartext within log files in the DEBUG folder when the application is placed in Debug mode for RDP connections. This exposes credentials that could be harvested by anyone with file system access to the DEBUG directory.

MitigationDisable Debug mode and remove any custom registry keys that enable debug logging. Rotate any credentials that may have been exposed. Implement strict access controls on the DEBUG folder to prevent unauthorized access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SecuraccessApplication
Affected:= 9.3.502

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm installed SecurAccess version
    Check the installed SecurEnvoy SecurAccess version on the system and verify it is exactly 9.3.502. This can typically be found in Add/Remove Programs, the SecurAccess administration console, or the application binary properties.
    Affected if The installed version is exactly 9.3.502 (other versions are not affected by this specific CVE).
  2. Identify if Debug mode is enabled
    Examine the SecurAccess configuration for Debug mode settings. This is typically controlled via registry keys (commonly under HKLM\SOFTWARE\SecurEnvoy or HKCU\SOFTWARE\SecurEnvoy) or configuration files in the SecurAccess installation directory. Look for keys such as 'Debug', 'DebugMode', 'EnableDebug', or similar debug-related entries.
    Affected if Debug mode is enabled on the SecurAccess installation.
  3. Locate the DEBUG folder
    Navigate to the SecurAccess installation directory and identify the presence of a 'DEBUG' folder. This folder is specifically created when Debug mode is active for RDP connections.
    Affected if A DEBUG folder exists within the SecurAccess installation directory.
  4. Inspect log files in DEBUG folder for credentials
    Examine all log files within the DEBUG folder for occurrences of emergency credentials, password strings, or authentication tokens stored in cleartext. Search for terms such as 'emergency', 'credential', 'password', 'passcode', or similar sensitive data patterns.
    Affected if Log files in the DEBUG folder contain cleartext emergency credentials or other sensitive authentication data.

A system is affected if it runs SecurEnvoy SecurAccess version 9.3.502 with Debug mode enabled and contains a DEBUG folder with log files showing cleartext emergency credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable Debug mode and remove any custom registry keys that enable debug logging. Rotate any credentials that may have been exposed. Implement strict access controls on the DEBUG folder to prevent unauthorized access.

Fix this in Securaccess Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-18466 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-18466 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data