{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-30367 exists.","fix":"No fix has been published for CVE-2023-30367 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-30367 is a high-severity vulnerability in n/a, published on 26 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-30367 and fix it if it is affected.\n\nWhat it is: CVE-2023-30367 is a high-severity vulnerability in n/a, published on 26 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-30367 exists.\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-2023-30367/ (Markdown: https://insights.sbomify.com/CVE-2023-30367/index.md)","id":"CVE-2023-30367","markdown":"https://insights.sbomify.com/CVE-2023-30367/index.md","name":"CVE-2023-30367","record":{"aliases":["GHSA-qmw7-qmmv-f8vj"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"mRemoteNG connection manager","requires_auth":"none","summary":"Attackers can dump memory to retrieve plaintext credentials from mRemoteNG configuration files if no custom encryption key is set.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mremoteng","vendor":"mremoteng"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"Multi-Remote Next Generation Connection Manager (mRemoteNG) is free software that enables users to store and manage multi-protocol connection configurations to remotely connect to systems. mRemoteNG configuration files can be stored in an encrypted state on disk. mRemoteNG version \u003c= v1.76.20 and \u003c= 1.77.3-dev loads configuration files in plain text into memory (after decrypting them if necessary) at application start-up, even if no connection has been established yet. This allows attackers to access contents of configuration files in plain text through a memory dump and thus compromise user credentials when no custom password encryption key has been set. This also bypasses the connection configuration file encryption setting by dumping already decrypted configurations from memory.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2023-07-08","github_poc":1,"max_poc_stars":18,"metasploit":0,"nuclei":0,"refs":[{"date":"2023-07-08T18:16:39Z","kind":"github_poc","ref":"https://github.com/S1lkys/CVE-2023-30367-mRemoteNG-password-dumper","stars":18,"title":"Original PoC for CVE-2023-30367"}],"tier":"weaponised"},"has_fix":false,"headline":"Information disclosure in n/a","id":"CVE-2023-30367","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"Memory corruption in n/a","id":"CVE-2023-30368"},"packages":[],"prev":{"headline":"Prototype Pollution in vConsole","id":"CVE-2023-30363"},"products":["n/a"],"published":"2023-07-26","related":[{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2020-24307","kev_date_added":null,"published":"2023-02-02"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-23","vendors":["n/a"]},"summary":"Attackers can dump memory to retrieve plaintext credentials from mRemoteNG configuration files if no custom encryption key is set.","url":"https://insights.sbomify.com/CVE-2023-30367/"}