Vulnerability report

Exploited in the wild High confidence Not in CISA KEV

CVE-2011-1968

Windows Denial of Service

Microsoft / Windows

Watch CVE-2011-1968 Browse KEV feed
Severity
CVSS 7.1 · High
Confidence
High
Exploit status
Exploited in the wild
EPSS
25.7%
First observed
—
Last observed
—

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2011-1968 is an unauthenticated vulnerability affecting Microsoft Windows. The Remote Desktop Protocol (RDP) implementation in Microsoft Windows XP SP2 and SP3 and Windows Server 2003 SP2 does not properly process...

Is it exploited?

Yes. Previdian tracks this CVE as a known exploited vulnerability. Confidence is high. Also confirmed by third-party sources.

Who is affected?

Microsoft / Windows.

What should we do?

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Overview

Windows Denial of Service

The Remote Desktop Protocol (RDP) implementation in Microsoft Windows XP SP2 and SP3 and Windows Server 2003 SP2 does not properly process packets in memory, which allows remote attackers to cause a denial of service (reboot) by sending crafted RDP packets triggering access to an object that (1) was not properly initialized or (2) is deleted, as exploited in the wild in 2011, aka "Remote Desktop Protocol Vulnerability."

View vendor advisory (opens in new tab)
Published
10 Aug 2011
Exploitation Reported
10 Aug 2011
Attack vector
Remote
Complexity
—
Privileges
None
User interaction
—

Tags

windows

CVE References

  • CVE Record CVE.org · CVE Record https://www.cve.org/CVERecord?id=CVE-2011-1968
  • MS11-065 docs.microsoft.com · Vendor Advisory https://docs.microsoft.com/en-us/security-updates/securitybulletins/2...
  • TA11-221A us-cert.gov · Third-Party Advisory http://www.us-cert.gov/cas/techalerts/TA11-221A.html
  • oval:org.mitre.oval:def:12806 oval.cisecurity.org · VDB Entry https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.m...

Exploitation evidence

Why Previdian marks this CVE as exploited

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploited in the wild

CVE

Recorded 10 Aug 2011

A trusted third party reported exploitation.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
CVE First 2011-08-10 21:16 UTC

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets
User-Agents
Callback hosts
0
0
0

Request targets and User-Agents available in Pro. Callback host details available in Enterprise.

Scanner coverage

No scanner integrations recorded yet.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

No detection artifacts or sensor request patterns are available for this CVE yet.

Check back as sensor telemetry and scanner integrations are updated.

Risk and context

Severity, weaknesses, and research context

CVSS v2.0

7.1 High

Potential damage if exploited. Separate from whether attackers are using it.

AV:N/AC:M/Au:N/C:N/I:N/A:C

EPSS

25.7%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

Weaknesses

Resource Management Errors CWE-399

Timeline

From disclosure to observed exploitation

  1. 21:16 UTC

    Added to Previdian KEV Feed

    High-confidence, third-party attested exploitation

  2. 21:16 UTC

    CVE published

    Vulnerability disclosed publicly

  3. 00:00 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

Start 14-day Pro trial Read API docs
  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2011-1968

Sample API response 
{
  "cve_id": "CVE-2011-1968",
  "confidence": "High",
  "cvss_score": 7.1,
  "cvss_estimated": false,
  "epss_score": 0.25708,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}