{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-15656 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-15656 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-15656 is a high-severity vulnerability in n/a, published on 5 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-15656 and fix it if it is affected.\n\nWhat it is: CVE-2018-15656 is a high-severity vulnerability in n/a, published on 5 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-15656 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-15656/ (Markdown: https://insights.sbomify.com/CVE-2018-15656/index.md)","id":"CVE-2018-15656","markdown":"https://insights.sbomify.com/CVE-2018-15656/index.md","name":"CVE-2018-15656","record":{"aliases":["GHSA-fvfr-96g6-xp99"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"MDM server","requires_auth":"none","summary":"An attacker can determine if user accounts exist by querying the registration API with a valid API key, exposing user existence information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"suremdm","vendor":"42gears"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"An issue was discovered in the registration API endpoint in 42Gears SureMDM before 2018-11-27. An attacker can submit a GET request to /api/register/:email, where :email is a base64 encoded e-mail address, to receive confirmation as to whether a user account exists in the system with the specified e-mail address. The request must be made with an \"apiKey\" value in the \"ApiKey\" header.","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-15656","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Server-side request forgery in n/a","id":"CVE-2018-15657"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2018-15655"},"products":["n/a"],"published":"2019-02-05","related":[{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2018-15658","kev_date_added":null,"published":"2019-02-05"},{"cvss_score":7.3,"headline":"Server-side request forgery in n/a","id":"CVE-2018-15657","kev_date_added":null,"published":"2019-02-05"},{"cvss_score":6.5,"headline":"Information disclosure in n/a","id":"CVE-2018-15655","kev_date_added":null,"published":"2019-02-05"},{"cvss_score":6.5,"headline":"Information disclosure in n/a","id":"CVE-2018-15659","kev_date_added":null,"published":"2019-02-05"},{"cvss_score":4.8,"headline":"Bypassing CAPTCHA \u0026 Enumerating Usernames via Password Reset Page","id":"CVE-2023-3897","kev_date_added":null,"published":"2023-07-25"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"An attacker can determine if user accounts exist by querying the registration API with a valid API key, exposing user existence information.","url":"https://insights.sbomify.com/CVE-2018-15656/"}