{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-8516 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-8516 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-8516 is a high-severity vulnerability in Microsoft Sql Server, published on 8 Aug 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-8516 and fix it if it is affected.\n\nWhat it is: CVE-2017-8516 is a high-severity vulnerability in Microsoft Sql Server, published on 8 Aug 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-8516 in the wild and no public exploit code.\n\nAffected product: Microsoft Sql Server. 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-8516/ (Markdown: https://insights.sbomify.com/CVE-2017-8516/index.md)","id":"CVE-2017-8516","markdown":"https://insights.sbomify.com/CVE-2017-8516/index.md","name":"CVE-2017-8516","record":{"aliases":["GHSA-qgr4-h86c-w3g3"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"SQL Server Analysis Services","requires_auth":"none","summary":"An attacker can access sensitive information due to improper permission enforcement in SQL Server Analysis Services.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"sql_server","vendor":"microsoft"}],"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-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Microsoft SQL Server Analysis Services in Microsoft SQL Server 2012, Microsoft SQL Server 2014, and Microsoft SQL Server 2016 allows an information disclosure vulnerability when it improperly enforces permissions, aka \"Microsoft SQL Server Analysis Services Information Disclosure Vulnerability\".","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 SQL Server","id":"CVE-2017-8516","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:sql_server","products":["microsoft:sql_server"],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in Microsoft browsers","id":"CVE-2017-8517"},"packages":[],"prev":{"headline":"Denial of service in Microsoft Windows","id":"CVE-2017-8515"},"products":["SQL Server"],"published":"2017-08-08","related":[{"cvss_score":9.8,"headline":"Microsoft SQL Server Reporting Services Remote Code Execution","id":"CVE-2020-0618","kev_date_added":"2024-09-18","published":"2020-02-11"},{"cvss_score":8.8,"headline":"Microsoft SQL Server Remote Code Execution","id":"CVE-2019-1068","kev_date_added":"2026-08-26","published":"2019-07-15"},{"cvss_score":9.8,"headline":"Memory corruption in Microsoft SQL Server","id":"CVE-2018-8273","kev_date_added":null,"published":"2018-08-15"},{"cvss_score":9,"headline":"Memory corruption in n/a","id":"CVE-2008-5416","kev_date_added":null,"published":"2008-12-10"},{"cvss_score":8.8,"headline":"Microsoft SQL Server Remote Code Execution Vulnerability","id":"CVE-2023-21705","kev_date_added":null,"published":"2023-02-14"},{"cvss_score":8.8,"headline":"Microsoft SQL Server Remote Code Execution Vulnerability","id":"CVE-2023-21713","kev_date_added":null,"published":"2023-02-14"},{"cvss_score":8.8,"headline":"Microsoft SQL Elevation of Privilege Vulnerability","id":"CVE-2021-1636","kev_date_added":null,"published":"2021-01-12"}],"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-09-16","vendors":["Microsoft Corporation"]},"summary":"An attacker can access sensitive information due to improper permission enforcement in SQL Server Analysis Services.","url":"https://insights.sbomify.com/CVE-2017-8516/"}