# CVE-2013-3918: Microsoft Windows Out-of-Bounds Write

> Remote attackers can execute arbitrary code or cause denial of service via a crafted web page exploiting an out-of-bounds write in the InformationCardSigninHelper ActiveX control.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 6 Oct 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Nov 2013
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-7627-vgq8-rcjv

## What is CVE-2013-3918?

CVE-2013-3918 is a high-severity memory corruption vulnerability in Microsoft Windows 7, published on 12 Nov 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The InformationCardSigninHelper Class ActiveX control in icardie.dll in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, and Windows RT Gold and 8.1 allows remote attackers to execute arbitrary code or cause a denial of service (out-of-bounds write) via a crafted web page that is accessed by Internet Explorer, as exploited in the wild in November 2013, aka "InformationCardSigninHelper Vulnerability."

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2013-3918?

It affects 10 products.


Products: Microsoft Windows 7, Microsoft Windows 8, Microsoft Windows 8.1, Microsoft Windows Rt, Microsoft Windows Rt 8.1, Microsoft Windows Server 2003, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Vista, Microsoft Windows Xp.

## How do I fix CVE-2013-3918?

No fix has been published for CVE-2013-3918 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 27 Oct 2025.

## Is CVE-2013-3918 being exploited?

Yes. Attackers have exploited CVE-2013-3918 in the wild since at least 6 Oct 2025.

Public exploit code:

- MS13-090 CardSpaceClaimCollection ActiveX Integer Underflow (metasploit)
- Microsoft Internet Explorer - CardSpaceClaimCollection ActiveX Integer Underflow (MS13-090) (Metasploit) (exploitdb)

## Other vulnerabilities in Microsoft Windows 7

- [CVE-2015-1635](https://insights.sbomify.com/CVE-2015-1635/): Microsoft HTTP.sys Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2015-2360](https://insights.sbomify.com/CVE-2015-2360/): Microsoft Win32k Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2014-6324](https://insights.sbomify.com/CVE-2014-6324/): Microsoft Kerberos Key Distribution Center (KDC) Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2014-6332](https://insights.sbomify.com/CVE-2014-6332/): Microsoft Windows Object Linking & Embedding (OLE) Automation Array Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2014-4148](https://insights.sbomify.com/CVE-2014-4148/): Microsoft Windows Remote Code Execution (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-3918 and fix it if it is affected.

What it is: CVE-2013-3918 is a high-severity memory corruption vulnerability in Microsoft Windows 7, published on 12 Nov 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2013-3918 in the wild since at least 6 Oct 2025.

Affected product: Microsoft Windows 7. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-3918/ (Markdown: https://insights.sbomify.com/CVE-2013-3918/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-3918
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-3918
- OSV: https://osv.dev/vulnerability/CVE-2013-3918

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-3918/
Summaries are generated and may contain mistakes; the official description above is the record.