Microsoft Silverlight 5 before 5.1.30214.0 and Silverlight 5 Developer Runtime before 5.1.30214.0 allow attackers to bypass the DEP and ASL…

published 2014-03-12 12y ago modified 2026-06-17 4mo ago also EUVD-2014-0357

cvss: 7.1; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 5.9%; EPSS 5.9% chance of exploitation in 30 days, percentile 93%
public exploits: 0; none known

Microsoft Silverlight 5 before 5.1.30214.0 and Silverlight 5 Developer Runtime before 5.1.30214.0 allow attackers to bypass the DEP and ASLR protection mechanisms via unspecified vectors, aka "Silverlight DEP/ASLR Bypass Vulnerability."

Is CVE-2014-0319 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

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

CVSS scores

assigned by	version	score	vector
NVD	2.0	7.1	AV:N/AC:M/Au:N/C:N/I:C/A:N

Classification

Weakness

CWE-264 Permissions, Privileges, and Access Controls

References

docs.microsoft.com /en-us/security-updates/securitybulletins/2014/ms14-014
vendor-advisory

Sources

CVE List CVE-2014-0319
NVD CVE-2014-0319

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.