{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-0996 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-0996 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-0996 is a medium-severity vulnerability in Microsoft Azure DevOps Server 2019, published on 12 Jun 2019. 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-2019-0996 and fix it if it is affected.\n\nWhat it is: CVE-2019-0996 is a medium-severity vulnerability in Microsoft Azure DevOps Server 2019, published on 12 Jun 2019. 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-2019-0996 in the wild and no public exploit code.\n\nAffected product: Microsoft Azure DevOps Server 2019. 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-2019-0996/ (Markdown: https://insights.sbomify.com/CVE-2019-0996/index.md)","id":"CVE-2019-0996","markdown":"https://insights.sbomify.com/CVE-2019-0996/index.md","name":"CVE-2019-0996","record":{"aliases":["GHSA-rm8m-fp2p-77cc"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Azure DevOps Server","requires_auth":"none","summary":"Attackers can bypass OAuth protections to register applications on behalf of users via cross-site request forgery in Azure DevOps Server.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"azure_devops_server","vendor":"microsoft"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"A spoofing vulnerability exists in Azure DevOps Server when it improperly handles requests to authorize applications, resulting in a cross-site request forgery. An attacker who successfully exploited this vulnerability could bypass OAuth protections and register an application on behalf of the targeted user.\nTo exploit this vulnerability, an attacker would need to create a page specifically designed to cause a cross-site request. The attacker would then need to convince a targeted user to click a link to the malicious page.\nThe update addresses the vulnerability by modifying how Azure DevOps Server protects application registration requests.","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":"Azure DevOps Server Spoofing Vulnerability","id":"CVE-2019-0996","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2019-0997"},"packages":[],"prev":{"headline":"Security feature bypass in Internet Explorer 11","id":"CVE-2019-0995"},"products":["Azure DevOps Server 2019"],"published":"2019-06-12","related":[{"cvss_score":9.8,"headline":"Code injection in Azure DevOps Server","id":"CVE-2019-1306","kev_date_added":null,"published":"2019-09-11"},{"cvss_score":9.8,"headline":"Code injection in Azure DevOps Server","id":"CVE-2019-1072","kev_date_added":null,"published":"2019-07-15"},{"cvss_score":8.8,"headline":"Azure DevOps Server Remote Code Execution Vulnerability","id":"CVE-2023-33136","kev_date_added":null,"published":"2023-09-12"},{"cvss_score":7.6,"headline":"Azure DevOps Server Spoofing Vulnerability","id":"CVE-2024-35266","kev_date_added":null,"published":"2024-07-09"},{"cvss_score":7.6,"headline":"Azure DevOps Server Spoofing Vulnerability","id":"CVE-2024-35267","kev_date_added":null,"published":"2024-07-09"},{"cvss_score":7.5,"headline":"Azure DevOps Server Remote Code Execution Vulnerability","id":"CVE-2024-20667","kev_date_added":null,"published":"2024-02-13"},{"cvss_score":7.5,"headline":"Azure DevOps Server Remote Code Execution Vulnerability","id":"CVE-2023-21553","kev_date_added":null,"published":"2023-02-14"}],"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":"2025-05-20","vendors":["Microsoft"]},"summary":"Attackers can bypass OAuth protections to register applications on behalf of users via cross-site request forgery in Azure DevOps Server.","url":"https://insights.sbomify.com/CVE-2019-0996/"}