{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-16629 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-16629 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-16629 is a high-severity vulnerability in n/a, published on 11 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-16629 and fix it if it is affected.\n\nWhat it is: CVE-2017-16629 is a high-severity vulnerability in n/a, published on 11 Aug 2021. 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-2017-16629 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-2017-16629/ (Markdown: https://insights.sbomify.com/CVE-2017-16629/index.md)","id":"CVE-2017-16629","markdown":"https://insights.sbomify.com/CVE-2017-16629/index.md","name":"CVE-2017-16629","record":{"aliases":["GHSA-f4x9-gw7p-923p"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"SapphireIMS","requires_auth":"none","summary":"Attackers can enumerate valid usernames in SapphireIMS by observing distinct error messages returned during login attempts.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sapphireims","vendor":"sapphireims"}],"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-209","name":"Generation of Error Message Containing Sensitive Information"}],"description":"In SapphireIMS 4097_1, it is possible to guess the registered/active usernames of the software from the errors it gives out for each type of user on the Login form. For \"Incorrect User\" - it gives an error \"The application failed to identify the user. Please contact administrator for help.\" For \"Correct User and Incorrect Password\" - it gives an error \"Authentication failed. Please login again.\"","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-2017-16629","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2017-16630"},"packages":[],"prev":{"headline":"Unsafe deserialization in owlmixin","id":"CVE-2017-16618"},"products":["n/a"],"published":"2021-08-11","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2020-25560","kev_date_added":null,"published":"2021-08-11"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2020-25563","kev_date_added":null,"published":"2021-08-11"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2020-25565","kev_date_added":null,"published":"2021-08-11"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2020-25566","kev_date_added":null,"published":"2021-08-11"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2017-16630","kev_date_added":null,"published":"2021-08-11"},{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2020-25564","kev_date_added":null,"published":"2021-08-11"},{"cvss_score":7.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2020-25561","kev_date_added":null,"published":"2021-08-11"}],"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":"Attackers can enumerate valid usernames in SapphireIMS by observing distinct error messages returned during login attempts.","url":"https://insights.sbomify.com/CVE-2017-16629/"}