FFmpeg prior 27.0.1453.93 libavcodec/h264.c denial of service

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.2$0-$5k0.00

Summaryinfo

A vulnerability described as problematic has been identified in FFmpeg. Affected by this vulnerability is an unknown functionality of the file libavcodec/h264.c. The manipulation results in denial of service. This vulnerability is reported as CVE-2013-2836. No exploit exists. A patch should be applied to remediate this issue.

Detailsinfo

A vulnerability was found in FFmpeg (Multimedia Processing Software). It has been classified as critical. Affected is an unknown code block of the file libavcodec/h264.c. The manipulation with an unknown input leads to a denial of service vulnerability. CWE is classifying the issue as CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. This is going to have an impact on availability. CVE summarizes:

Multiple unspecified vulnerabilities in Google Chrome before 27.0.1453.93 allow attackers to cause a denial of service or possibly have other impact via unknown vectors.

The weakness was disclosed 02/20/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as 241595 as confirmed git commit (Website). The advisory is available at code.google.com. The public release has been coordinated in cooperation with the vendor. This vulnerability is traded as CVE-2013-2836 since 04/11/2013. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit.

The vulnerability scanner Nessus provides a plugin with the ID 66549 (FreeBSD : chromium -- multiple vulnerabilities (358133b5-c2b9-11e2-a738-00262d5ed8ee)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family FreeBSD Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 121201 (Google Chrome Prior to 27.0.1453.93 Multiple Vulnerabilities).

Upgrading to version 27.0.1453.93 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.videolan.org. The best possible mitigation is suggested to be patching the affected component. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (66549), SecurityFocus (BID 60062†), OSVDB (94001†) and Secunia (SA53430†). The entries VDB-8503, VDB-8559, VDB-8661 and VDB-8840 are pretty similar. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Affected

  • Google Chrome 26.0.1410.63
  • Google Chrome 26.0.1410.64
  • Google Chrome 26.0.1410.65

Productinfo

Type

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.5
VulDB Meta Temp Score: 7.2

VulDB Base Score: 7.5
VulDB Temp Score: 7.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Denial of service
CWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 66549
Nessus Name: FreeBSD : chromium -- multiple vulnerabilities (358133b5-c2b9-11e2-a738-00262d5ed8ee)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 803705
OpenVAS Name: Google Chrome Multiple Vulnerabilities-01 May13 (Linux)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: FFmpeg 27.0.1453.93
Patch: git.videolan.org

Timelineinfo

02/20/2013 🔍
02/20/2013 +0 days 🔍
04/11/2013 +50 days 🔍
05/21/2013 +40 days 🔍
05/22/2013 +1 days 🔍
05/23/2013 +1 days 🔍
06/10/2013 +18 days 🔍
04/24/2019 +2144 days 🔍

Sourcesinfo

Product: ffmpeg.org

Advisory: 241595
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2013-2836 (🔍)
GCVE (CVE): GCVE-0-2013-2836
GCVE (VulDB): GCVE-100-9042

OVAL: 🔍

SecurityFocus: 60062 - Google Chrome CVE-2013-2836 Multiple Unspecified Security Vulnerabilities
Secunia: 53430 - Google Chrome Multiple Vulnerabilities, Highly Critical
OSVDB: 94001

See also: 🔍

Entryinfo

Created: 06/10/2013 10:53
Updated: 04/24/2019 06:56
Changes: 06/10/2013 10:53 (81), 04/24/2019 06:56 (2)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!