{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-18466 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-18466 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2018-18466 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2018-18466 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2018-18466/ (Markdown: https://insights.sbomify.com/CVE-2018-18466/index.md)","id":"CVE-2018-18466","markdown":"https://insights.sbomify.com/CVE-2018-18466/index.md","name":"CVE-2018-18466","record":{"aliases":["GHSA-8wpj-w799-92rg"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"SecurEnvoy SecurAccess","requires_auth":"low_privilege","summary":"An attacker with local access can read emergency credentials from debug logs if the application is configured in debug mode.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"securaccess","vendor":"securenvoy"}],"cvss":{"score":7,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2018-18466","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2018-18467"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2018-18461"},"products":["n/a"],"published":"2019-03-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-30","vendors":["n/a"]},"summary":"An attacker with local access can read emergency credentials from debug logs if the application is configured in debug mode.","url":"https://insights.sbomify.com/CVE-2018-18466/"}