CVE-2013-6631: n/a vulnerability

CVE-2013-6631: Use-after-free vulnerability in the Channel::SendRTCPPacket function in voice_engine/channel.cc in libjingl...

Use-after-free vulnerability in the Channel::SendRTCPPacket function in voice_engine/channel.cc in libjingle in WebRTC, as used in Google Chrome before 31.0.1650.48 and other products, allows remote attackers to cause a denial of service (heap memory corruption) or possibly have unspecified other impact via vectors that trigger the absence of certain statistics initialization, leading to the skipping of a required DeRegisterExternalTransport call.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 17:46 UTC (UTC+00:00)

Security readout for executives and security teams

CVE-2013-6631 is an old WebRTC/libjingle memory-safety flaw affecting Google Chrome before 31.0.1650.48 and potentially other products using that code. A remote attacker could crash the affected component and might cause other unspecified effects. The provided sources do not show active exploitation. Current exposure is most likely in legacy Chrome installations, old Linux distribution packages, embedded browser components, or products carrying an outdated WebRTC/libjingle fork. Modern, supported browsers are unlikely to be exposed unless they retained the vulnerable code path. Treat this as legacy technical debt unless old WebRTC-based software remains in use. Prioritize remediation for exposed browsers, kiosks, embedded clients, or unmanaged endpoints. No active exploitation evidence is provided, but remote memory corruption warrants cleanup when found. Mitigation focus: Upgrade Chrome to 31.0.1650.48 or later where applicable.; Update any WebRTC/libjingle-consuming product through its vendor-supported channel.; Apply relevant Debian or openSUSE security updates for affected packages..

Prepared: Jun 14, 2026, 15:13 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2013-6631 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Nov 15, 2013, 20:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://code.google.com/p/webrtc/source/detail?r=4827CVE reference · x_refsource_CONFIRM
https://code.google.com/p/chromium/issues/detail?id=296804CVE reference · x_refsource_CONFIRM
https://webrtc-codereview.appspot.com/2275008CVE reference · x_refsource_CONFIRM

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.