CVE-2013-1279: Race Condition
First published: Wed Feb 13 2013(Updated: )
Race condition in the kernel in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2, R2, and R2 SP1, Windows 7 Gold and SP1, Windows 8, Windows Server 2012, and Windows RT allows local users to gain privileges via a crafted application that leverages incorrect handling of objects in memory, aka "Kernel Race Condition Vulnerability," a different vulnerability than CVE-2013-1278.
Credit: secure@microsoft.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Microsoft Windows 7 | ||
| Microsoft Windows 7 | ||
| Microsoft Windows 7 | =sp1 | |
| Microsoft Windows 7 | =sp1 | |
| Microsoft Windows Server | =sp2 | |
| Microsoft Windows Server | =r2 | |
| Microsoft Windows Server | =r2 | |
| Microsoft Windows Server | =sp2 | |
| Microsoft Windows Server | =sp2 | |
| Microsoft Windows Server | =sp2 | |
| Microsoft Windows Vista | =sp2 | |
| Microsoft Windows XP | =sp3 | |
| Microsoft Windows XP | =sp2 | |
| Microsoft Windows Vista | =sp2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2013-1279?
CVE-2013-1279 is considered to be of high severity due to its potential to allow local users to gain elevated privileges.
How do I fix CVE-2013-1279?
To fix CVE-2013-1279, apply the security updates provided by Microsoft for the affected operating systems.
Which versions of Windows are affected by CVE-2013-1279?
CVE-2013-1279 affects various versions including Windows XP SP2 and SP3, Windows Vista SP2, Windows Server 2003 SP2, Windows 7, Windows 8, and Windows Server 2012.
Can CVE-2013-1279 be exploited remotely?
CVE-2013-1279 requires local access to the system, so it cannot be exploited remotely.
Are there any workarounds for CVE-2013-1279 if I can't apply the update?
There are no specific workarounds recommended for CVE-2013-1279, thus applying the security update is the best course of action.
- agent/type
- agent/last-modified-date
- agent/first-publish-date
- agent/references
- agent/severity
- agent/weakness
- agent/description
- agent/event
- agent/tags
- collector/nvd-api
- agent/software-canonical-lookup-request
- collector/nvd-index
- agent/author
- agent/softwarecombine
- vendor/microsoft
- canonical/microsoft windows 7
- version/microsoft windows 7/sp1
- canonical/microsoft windows server
- version/microsoft windows server/sp2
- version/microsoft windows server/r2
- canonical/microsoft windows vista
- version/microsoft windows vista/sp2
- canonical/microsoft windows xp
- version/microsoft windows xp/sp3
- version/microsoft windows xp/sp2