{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-11693 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-11693 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-11693 is a critical vulnerability in n/a, published on 28 Jul 2017. 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-11693 and fix it if it is affected.\n\nWhat it is: CVE-2017-11693 is a critical vulnerability in n/a, published on 28 Jul 2017. 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-11693 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-11693/ (Markdown: https://insights.sbomify.com/CVE-2017-11693/index.md)","id":"CVE-2017-11693","markdown":"https://insights.sbomify.com/CVE-2017-11693/index.md","name":"CVE-2017-11693","record":{"aliases":["GHSA-38r9-78fx-p9qv"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"MEDHOST Document Management","requires_auth":"none","summary":"Hard-coded database credentials in MEDHOST Document Management System allow attackers to access and modify sensitive patient and financial data.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"medhost_document_management_system","vendor":"medhost"}],"cvss":{"score":9.1,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"MEDHOST Document Management System contains hard-coded credentials that are used for customer database access. An attacker with knowledge of the hard-coded credentials and the ability to communicate directly with the database may be able to obtain or modify sensitive patient and financial information. PostgreSQL is used as the Document Management System database. The account name is dms. The password is hard-coded throughout the application, and is the same across all installations. Customers do not have the option to change passwords. The dms account for PostgreSQL has access to the database schema for Document Management System.","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":"Hardcoded credentials in n/a","id":"CVE-2017-11693","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2017-11694"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2017-11692"},"products":["n/a"],"published":"2017-07-28","related":[{"cvss_score":9.1,"headline":"Hardcoded credentials in n/a","id":"CVE-2017-11694","kev_date_added":null,"published":"2017-07-28"}],"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":"Hard-coded database credentials in MEDHOST Document Management System allow attackers to access and modify sensitive patient and financial data.","url":"https://insights.sbomify.com/CVE-2017-11693/"}