LiveActive security incident?Get immediate response
CVE Record

CVE-2013-3670: The rle_unpack function in vmdav.c in libavcodec in FFmpeg git 20130328 through 20130501 does not properly...

The rle_unpack function in vmdav.c in libavcodec in FFmpeg git 20130328 through 20130501 does not properly use the bytestream2 API, which allows remote attackers to cause a denial of service (out-of-bounds array access and application crash) via crafted RLE data. NOTE: the vendor has listed this as an issue fixed in 1.2.1, but the issue is actually in new code that was not shipped with the 1.2.1 release or any earlier release.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is an old FFmpeg denial-of-service issue in development code from 2013. Crafted RLE media data could crash an application using the vulnerable libavcodec code. The source notes the bug was not shipped in FFmpeg 1.2.1 or earlier releases, so exposure is mainly custom builds from the affected git window. Likely limited to organizations that built or embedded FFmpeg directly from the affected 2013 git range. Standard packaged releases are less likely exposed based on the CVE note, which says the issue was not in 1.2.1 or earlier releases. Treat as a low-priority legacy exposure check unless your environment uses custom FFmpeg builds from the affected 2013 git window. Business impact is application crash or service interruption, with no source evidence of active exploitation or data compromise. Mitigation focus: Inventory applications and appliances embedding FFmpeg or libavcodec.; Check whether any builds came from FFmpeg git 20130328 through 20130501.; Use a supported FFmpeg release or code containing the referenced fixes..

Prepared

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-3670 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
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
1Source links

CVSS and timeline data

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

Source materials

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.