{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2018-1037 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-1037 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-1037 is a medium-severity vulnerability in Microsoft Visual Studio, published on 12 Apr 2018. 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-2018-1037 and fix it if it is affected.\n\nWhat it is: CVE-2018-1037 is a medium-severity vulnerability in Microsoft Visual Studio, published on 12 Apr 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-1037 in the wild and no public exploit code.\n\nAffected product: Microsoft Visual Studio. 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-2018-1037/ (Markdown: https://insights.sbomify.com/CVE-2018-1037/index.md)","id":"CVE-2018-1037","markdown":"https://insights.sbomify.com/CVE-2018-1037/index.md","name":"CVE-2018-1037","record":{"aliases":["GHSA-mrwc-m279-7475"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Microsoft Visual Studio","requires_auth":"none","summary":"Attackers can read uninitialized memory contents when Visual Studio compiles PDB files, potentially exposing sensitive data.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"visual_studio","vendor":"microsoft"},{"product":"visual_studio_2017","vendor":"microsoft"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-908","name":"Use of Uninitialized Resource"}],"description":"An information disclosure vulnerability exists when Visual Studio improperly discloses limited contents of uninitialized memory while compiling program database (PDB) files, aka \"Microsoft Visual Studio Information Disclosure Vulnerability.\" This affects Microsoft Visual Studio.","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 Microsoft Visual Studio","id":"CVE-2018-1037","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:visual_studio","products":["microsoft:visual_studio","microsoft:visual_studio_2017"],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Privilege escalation in Windows","id":"CVE-2018-1038"},"packages":[],"prev":{"headline":"Privilege escalation in Windows 10","id":"CVE-2018-1036"},"products":["Microsoft Visual Studio"],"published":"2018-04-12","related":[{"cvss_score":8.8,"headline":"Visual Studio Elevation of Privilege Vulnerability","id":"CVE-2025-49739","kev_date_added":null,"published":"2025-07-08"},{"cvss_score":8.8,"headline":"Visual Studio Remote Code Execution Vulnerability","id":"CVE-2022-35777","kev_date_added":null,"published":"2022-08-09"},{"cvss_score":8.8,"headline":"Visual Studio Remote Code Execution Vulnerability","id":"CVE-2022-35825","kev_date_added":null,"published":"2022-08-09"},{"cvss_score":8.8,"headline":"Visual Studio Remote Code Execution Vulnerability","id":"CVE-2022-35826","kev_date_added":null,"published":"2022-08-09"},{"cvss_score":8.8,"headline":"Visual Studio Remote Code Execution Vulnerability","id":"CVE-2022-35827","kev_date_added":null,"published":"2022-08-09"},{"cvss_score":7.8,"headline":"Visual Studio Elevation of Privilege Vulnerability","id":"CVE-2024-20656","kev_date_added":null,"published":"2024-01-09"},{"cvss_score":7.8,"headline":"Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability","id":"CVE-2021-28313","kev_date_added":null,"published":"2021-04-13"}],"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":["Microsoft"]},"summary":"Attackers can read uninitialized memory contents when Visual Studio compiles PDB files, potentially exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2018-1037/"}