{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-5683 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-5683 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-5683 is a high-severity vulnerability in n/a, published on 26 Aug 2016. 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-2016-5683 and fix it if it is affected.\n\nWhat it is: CVE-2016-5683 is a high-severity vulnerability in n/a, published on 26 Aug 2016. 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-2016-5683 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-2016-5683/ (Markdown: https://insights.sbomify.com/CVE-2016-5683/index.md)","id":"CVE-2016-5683","markdown":"https://insights.sbomify.com/CVE-2016-5683/index.md","name":"CVE-2016-5683","record":{"aliases":["GHSA-qcrp-q3mm-gq78"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"ReadyDesk web application","requires_auth":"low_privilege","summary":"Local attackers can extract cleartext SQL Server credentials by reading a configuration file and using a hardcoded key, compromising database security.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"certcc","cpe":[{"product":"readydesk","vendor":"readydesk"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"ReadyDesk 9.1 allows local users to determine cleartext SQL Server credentials by reading the SQL_Config.aspx file and decrypting data with a hardcoded key in the ReadyDesk.dll file.","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-2016-5683","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2016"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in FreeImage","id":"CVE-2016-5684"},"packages":[],"prev":{"headline":"Cross-Site Scripting in swagger-ui","id":"CVE-2016-5682"},"products":["n/a"],"published":"2016-08-26","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2016-5048","kev_date_added":null,"published":"2016-08-26"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2016-5050","kev_date_added":null,"published":"2016-08-26"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2016-5049","kev_date_added":null,"published":"2016-08-26"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Local attackers can extract cleartext SQL Server credentials by reading a configuration file and using a hardcoded key, compromising database security.","url":"https://insights.sbomify.com/CVE-2016-5683/"}