{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2002-1138 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2002-1138 yet. Limit exposure of the affected software until one is available.","what":"CVE-2002-1138 is a high-severity vulnerability in Microsoft Sql Server, published on 1 Sep 2004. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2002-1138 and fix it if it is affected.\n\nWhat it is: CVE-2002-1138 is a high-severity vulnerability in Microsoft Sql Server, published on 1 Sep 2004. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2002-1138 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-2002-1138/ (Markdown: https://insights.sbomify.com/CVE-2002-1138/index.md)","id":"CVE-2002-1138","markdown":"https://insights.sbomify.com/CVE-2002-1138/index.md","name":"CVE-2002-1138","record":{"aliases":["GHSA-3x48-6948-gjj7"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Microsoft SQL Server","requires_auth":"low_privilege","summary":"Attackers can overwrite system files by exploiting SQL Server's job output handling, leading to privilege escalation.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"data_engine","vendor":"microsoft"},{"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":"Microsoft SQL Server 7.0 and 2000, including Microsoft Data Engine (MSDE) 1.0 and Microsoft Desktop Engine (MSDE) 2000, writes output files for scheduled jobs under its own privileges instead of the entity that launched it, which allows attackers to overwrite system files, aka \"Flaw in Output File Handling for Scheduled Jobs.\"","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":"Privilege escalation in n/a","id":"CVE-2002-1138","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:sql_server","products":["microsoft:sql_server"],"type":"privilege_escalation","year":"2002"},"n_packages":0,"n_references":3,"next":{"headline":"Path traversal in n/a","id":"CVE-2002-1139"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2002-1137"},"products":["n/a"],"published":"2004-09-01","related":[{"cvss_score":10,"headline":"Privilege escalation in n/a","id":"CVE-2002-1145","kev_date_added":null,"published":"2002-10-21"},{"cvss_score":10,"headline":"Privilege escalation in n/a","id":"CVE-2002-0721","kev_date_added":null,"published":"2002-08-20"},{"cvss_score":9,"headline":"Memory corruption in n/a","id":"CVE-2008-0086","kev_date_added":null,"published":"2008-07-08"},{"cvss_score":9,"headline":"Memory corruption in n/a","id":"CVE-2008-0106","kev_date_added":null,"published":"2008-07-08"},{"cvss_score":9,"headline":"Integer overflow in n/a","id":"CVE-2008-0107","kev_date_added":null,"published":"2008-07-08"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2002-1123","kev_date_added":null,"published":"2004-09-01"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2002-1137","kev_date_added":null,"published":"2004-09-01"}],"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-08","vendors":["n/a"]},"summary":"Attackers can overwrite system files by exploiting SQL Server's job output handling, leading to privilege escalation.","url":"https://insights.sbomify.com/CVE-2002-1138/"}