LiveActive security incident?Get immediate response
CVE Record

CVE-2018-18466: An issue was discovered in SecurEnvoy SecurAccess 9.3.502.

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This issue concerns SecurEnvoy SecurAccess 9.3.502. Under debug-mode RDP troubleshooting conditions, emergency credentials may be written to local debug logs in cleartext. The vendor disputes the vulnerability because the condition reportedly requires administrator access and a support-provided registry key.

Executive priority

Treat this as a targeted configuration and log-exposure risk, not a confirmed internet-scale emergency. Prioritize review where SecurAccess protects privileged RDP access or where debug troubleshooting was recently performed.

Technical view

The reported behavior occurs when SecurAccess 9.3.502 is in Debug mode for RDP connections. Cleartext emergency credentials or passcodes are stored in logs under the DEBUG folder. Public sources do not provide CVSS, confirmed affected CPEs, or a patch statement.

Likely exposure

Exposure appears limited to SecurAccess 9.3.502 deployments using RDP with debug mode enabled and the custom support registry key present. Systems without that troubleshooting configuration may not be exposed based on the available description.

Exploitation context

There is no KEV listing and no cited evidence of active exploitation. The main risk is local disclosure from debug logs, especially if log access is broad or retained after troubleshooting.

Researcher notes

The record contains a vendor dispute and lacks severity scoring. Validate only the documented condition: SecurAccess 9.3.502, RDP use, debug mode, and the support registry key. Avoid broad claims beyond those sources.

Mitigation direction

  • Check SecurEnvoy or Thales guidance for supported remediation.
  • Disable debug mode when troubleshooting is complete.
  • Remove any support-provided debug registry key after use.
  • Restrict access to SecurAccess DEBUG logs.
  • Rotate emergency passcodes found in retained debug logs.

Validation and detection

  • Inventory SecurAccess installations and versions.
  • Identify deployments using SecurAccess for RDP connections.
  • Confirm whether debug mode is enabled.
  • Check whether the custom support registry key exists.
  • Review DEBUG folder logs for exposed emergency passcodes.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-18466 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.