How severe is CVE-2013-3182?

No CVSS score has been assigned to CVE-2013-3182 yet. Review the advisory details and affected package list to assess your exposure.

Which products are affected by CVE-2013-3182?

CVE-2013-3182 affects the following products: microsoft windows server 2012.

How do I patch CVE-2013-3182?

No patch has shipped for CVE-2013-3182 yet — track the microsoft windows server 2012 advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2013-3182 across my infrastructure?

Inventory every microsoft windows server 2012 deployment and check each version against the affected-products list above.

How do I mitigate CVE-2013-3182 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Is CVE-2013-3182 actively exploited in the wild?

No public exploit code has been indexed for CVE-2013-3182 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2013-3182?

CVE-2013-3182 has an EPSS (Exploit Prediction Scoring System) score of 94.6%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2013-3182?

CVE-2013-3182 is classified as Buffer Overflow (CWE-119). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2013-3182?

CVE-2013-3182 affects microsoft windows server 2012. Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2013-3182 published, and has it been updated?

CVE-2013-3182 was published on August 14, 2013 and was last updated on June 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2013-3182 — Windows Server 2012

CVE-2013-3182 is a Buffer Overflow vulnerability in microsoft windows server 2012. EPSS puts its 30-day exploitation probability at 94.6% (100th percentile). No vendor fix is recorded yet; mitigation options are listed below.

The Windows NAT Driver (aka winnat) service in Microsoft Windows Server 2012 does not properly validate memory addresses during the processing of ICMP packets, which allows remote attackers…

Published

Aug 14, 2013

Updated

Jun 16, 2026

Affected

1 product

Patched

See advisory

Exploits

None indexed

Exploitation data as of Oct 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

94.6%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

The Windows NAT Driver (aka winnat) service in Microsoft Windows Server 2012 does not properly validate memory addresses during the processing of ICMP packets, which allows remote attackers to cause a denial of service (memory corruption and system hang) via crafted packets, aka "Windows NAT Denial of Service Vulnerability."

Affected Products

1 product · 1 configurations

windows server 2012microsoft

all

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every microsoft windows server 2012 deployment and check each version against the affected-products list above.
Remediation status
No patch has shipped for CVE-2013-3182 yet — track the microsoft windows server 2012 advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2013-3182 being exploited in your environment?

Detect and block the exploit chain at execution, on systems you cannot patch yet.

Protect my workloads How runtime protection works