dbcve.org
LyncApplication · Microsoft

CVE-2013-1302

HIGH · 9.3 CVSS v2.0 Published 2013-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Microsoft Communicator 2007 R2, Lync 2010, Lync 2010 Attendee, and Lync Server 2013 do not properly handle objects in memory, which allows remote attackers to execute arbitrary code via an invitation that triggers access to a deleted object, aka "Lync RCE Vulnerability."

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Use-after-free memory corruption vulnerability in Microsoft Lync/Communicator clients and Lync Server. Attackers can achieve remote code execution by sending a specially crafted meeting invitation that triggers access to a deleted object in memory, allowing arbitrary code execution on the victim system.

MitigationApply Microsoft security updates from MS13-024 (Cumulative update for Lync). As an interim control, disable or filter Lync meeting invitations from untrusted sources until patches are deployed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LyncApplication
Affected:= 2010
Lync ServerApplication
Affected:= 2013
Office CommunicatorApplication
Affected:= 2007

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Microsoft Lync or Communicator client
    Open Programs and Features (appwiz.cpl) or check Add/Remove Programs, look for Microsoft Lync 2010, Microsoft Office Communicator 2007, or Microsoft Lync 2013 (if client)
    Affected if Product name matches Lync 2010, Office Communicator 2007, or Lync 2013 client
  2. Check installed Lync Server version
    Open Programs and Features or check Add/Remove Programs, look for Microsoft Lync Server 2013 components (e.g., Lync Server Front-End, Lync Server Administration Tools)
    Affected if Lync Server 2013 is installed
  3. Verify exact version number of Lync client
    Launch Lync/Communicator, go to File > Help > About Microsoft Lync, or check registry under HKLM\SOFTWARE\Microsoft\Office\Lync (for Lync 2010) or HKLM\SOFTWARE\Microsoft\Office\15.0\Lync (for Lync 2013)
    Affected if Version is 2010 (any build) or 2013 client (any build)
  4. Confirm meeting invitation feature is enabled
    In Lync/Communicator, go to Options > Personal (or Meetings), verify that meeting invitations can be received, or check if external/meeting invites are not blocked at the server/edge level
    Affected if Meeting invitations are allowed (default configuration)
  5. Inspect Lync Server meeting configuration
    In Lync Server Management Shell, run Get-CsMeetingConfiguration to review meeting policy settings, or check if external federation is enabled allowing meeting invites from untrusted sources
    Affected if External meeting invitations or federation is enabled

Your environment is affected if you have Lync 2010, Office Communicator 2007, or Lync 2013 (client or Server) installed and meeting invitations are permitted in your configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft security updates from MS13-024 (Cumulative update for Lync). As an interim control, disable or filter Lync meeting invitations from untrusted sources until patches are deployed.

Recommended fix Moderate confidence

Migrate to Microsoft Teams (cloud) or Skype for Business Server 2019 (on-premises)

  1. Identify all systems running the affected Microsoft Lync or Communicator products (Lync 2010, Lync 2010 Attendee, Lync Server 2013, Communicator 2007 R2)
  2. Take inventory of integration points and dependencies with other systems
  3. Develop migration plan to supported communication platform (Microsoft Teams or Skype for Business Server 2019)
  4. Schedule maintenance window for migration
  5. Backup existing configurations and user data
  6. Deploy upgrade to Microsoft Teams or migrate to Skype for Business Server 2019
  7. Verify functionality post-migration
  8. Update documentation and inform users of new client
Caveat Legacy Lync/Communicator clients will not connect after migration; users must transition to Teams or SfB clients; custom integrations may require updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Lync Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-1302 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-1302 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data