hxds.dll in Microsoft Office 2007 SP3 and 2010 SP1 and SP2 does not implement the ASLR protection mechanism, which makes it easier for remo…

published 2013-12-11 12y ago modified 2026-06-16 4mo ago also EUVD-2013-4899

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

hxds.dll in Microsoft Office 2007 SP3 and 2010 SP1 and SP2 does not implement the ASLR protection mechanism, which makes it easier for remote attackers to execute arbitrary code via a crafted COM component on a web site that is visited with Internet Explorer, as exploited in the wild in December 2013, aka "HXDS ASLR Vulnerability."

Is CVE-2013-5057 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

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

CVSS scores

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

Classification

Weakness

CWE-264 Permissions, Privileges, and Access Controls

References

docs.microsoft.com /en-us/security-updates/securitybulletins/2013/ms13-106
vendor-advisory
blogs.technet.com /b/srd/archive/2013/12/09/ms13-106-another-aslr-bypass-is-gone.aspx
vendor-advisory

Sources

CVE List CVE-2013-5057
NVD CVE-2013-5057

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.