What is the CVSS score of CVE-2014-6440?

CVE-2014-6440 has a CVSS 3.0 base score of 9.8 (Critical). CVSS vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 5.3%.

Is there a public PoC exploit available for CVE-2014-6440?

Yes, a public proof-of-concept exploit is available for CVE-2014-6440. Prioritise patching immediately. EPSS: 5.3%.

Is there a patch available for CVE-2014-6440?

Yes, a patch is available for CVE-2014-6440. Update the affected software to the latest version immediately.

Vlc CVE-2014-6440

CRITICAL

Buffer Overflow (CWE-119)

2017-03-28 cve@mitre.org

Buffer Overflow RCE Denial Of Service Vlc

9.8

CVSS 3.0 · NVD

Severity by source

NVD PRIMARY

9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Mar 28, 2017 - 15:59 cve.org

CRITICAL 9.8

DescriptionCVE.org

VideoLAN VLC media player before 2.1.5 allows remote attackers to execute arbitrary code or cause a denial of service.

AnalysisAI

VideoLAN VLC media player before 2.1.5 allows remote attackers to execute arbitrary code or cause a denial of service. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.

Technical ContextAI

This vulnerability is classified as Buffer Overflow (CWE-119), which allows attackers to corrupt memory to execute arbitrary code or crash the application. VideoLAN VLC media player before 2.1.5 allows remote attackers to execute arbitrary code or cause a denial of service. Affected products include: Videolan Vlc. Version information: before 2.1.5.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Use memory-safe languages or bounds-checking. Enable ASLR, DEP/NX, stack canaries. Use safe string functions.