{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-0187 exists.","fix":"No fix has been published for CVE-2002-0187 yet. Limit exposure of the affected software until one is available.","what":"CVE-2002-0187 is a high-severity cross-site scripting vulnerability in Microsoft Sql Server, published on 2 Apr 2003. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2002-0187 and fix it if it is affected.\n\nWhat it is: CVE-2002-0187 is a high-severity cross-site scripting vulnerability in Microsoft Sql Server, published on 2 Apr 2003. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-0187 exists.\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-2002-0187/ (Markdown: https://insights.sbomify.com/CVE-2002-0187/index.md)","id":"CVE-2002-0187","markdown":"https://insights.sbomify.com/CVE-2002-0187/index.md","name":"CVE-2002-0187","record":{"aliases":["GHSA-vg32-84gw-2fph"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Microsoft SQL Server","requires_auth":"none","summary":"An attacker can execute arbitrary script in the SQLXML component via a crafted XML query, requiring user interaction to trigger.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sql_server","vendor":"microsoft"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Cross-site scripting vulnerability in the SQLXML component of Microsoft SQL Server 2000 allows an attacker to execute arbitrary script via the root parameter as part of an XML SQL query, aka \"Script Injection via XML Tag.\"","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2002-06-12","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2002-06-12","kind":"exploitdb","ref":"21541","stars":null,"title":"Microsoft SQL Server 2000 - SQLXML Script Injection"}],"tier":"weaponised"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2002-0187","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:sql_server","products":["microsoft:sql_server"],"type":"xss","year":"2002"},"n_packages":0,"n_references":3,"next":{"headline":"Code injection in n/a","id":"CVE-2002-0188"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2002-0186"},"products":["n/a"],"published":"2003-04-02","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":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"An attacker can execute arbitrary script in the SQLXML component via a crafted XML query, requiring user interaction to trigger.","url":"https://insights.sbomify.com/CVE-2002-0187/"}