A spoofing vulnerability that could allow a security feature bypass exists in when Azure DevOps Server does not properly sanitize user prov…

published 2019-04-09 7y ago modified 2026-06-17 4mo ago also EUVD-2019-1608

cvss: 6.5; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 3.9%; EPSS 3.9% chance of exploitation in 30 days, percentile 90%
public exploits: 0; none known

A spoofing vulnerability that could allow a security feature bypass exists in when Azure DevOps Server does not properly sanitize user provided input, aka 'Azure DevOps Server Spoofing Vulnerability'.

Patch / fix

links 1

portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0857 advisory

Is CVE-2019-0857 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

3.86% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	6.5	CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:N/I:P/A:N

Affected products

Microsoft Azure DevOps Server

Classification

Weakness

CWE-116 Improper Encoding or Escaping of Output

References

portal.msrc.microsoft.com /en-US/security-guidance/advisory/CVE-2019-0857
patch, vendor-advisory
securityfocus.com /bid/107760
vdb-entry, third-party-advisory

Sources

CVE List CVE-2019-0857
NVD CVE-2019-0857

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.