CVE-2014-3157CVE-2014-3157

Affected configuration(s):

cpe:/a:google:chrome:35.0.1916.0
cpe:/a:google:chrome:35.0.1916.1
cpe:/a:google:chrome:35.0.1916.2
cpe:/a:google:chrome:35.0.1916.3
cpe:/a:google:chrome:35.0.1916.4
cpe:/a:google:chrome:35.0.1916.5
cpe:/a:google:chrome:35.0.1916.6
cpe:/a:google:chrome:35.0.1916.7
cpe:/a:google:chrome:35.0.1916.8
cpe:/a:google:chrome:35.0.1916.9
cpe:/a:google:chrome:35.0.1916.10
cpe:/a:google:chrome:35.0.1916.11
cpe:/a:google:chrome:35.0.1916.13
cpe:/a:google:chrome:35.0.1916.14
cpe:/a:google:chrome:35.0.1916.15
cpe:/a:google:chrome:35.0.1916.17
cpe:/a:google:chrome:35.0.1916.18
cpe:/a:google:chrome:35.0.1916.19
cpe:/a:google:chrome:35.0.1916.20
cpe:/a:google:chrome:35.0.1916.21
cpe:/a:google:chrome:35.0.1916.22
cpe:/a:google:chrome:35.0.1916.23
cpe:/a:google:chrome:35.0.1916.27
cpe:/a:google:chrome:35.0.1916.31
cpe:/a:google:chrome:35.0.1916.32
cpe:/a:google:chrome:35.0.1916.33
cpe:/a:google:chrome:35.0.1916.34
cpe:/a:google:chrome:35.0.1916.35
cpe:/a:google:chrome:35.0.1916.36
cpe:/a:google:chrome:35.0.1916.37
cpe:/a:google:chrome:35.0.1916.38
cpe:/a:google:chrome:35.0.1916.39
cpe:/a:google:chrome:35.0.1916.40
cpe:/a:google:chrome:35.0.1916.41
cpe:/a:google:chrome:35.0.1916.42
cpe:/a:google:chrome:35.0.1916.43
cpe:/a:google:chrome:35.0.1916.44
cpe:/a:google:chrome:35.0.1916.45
cpe:/a:google:chrome:35.0.1916.46
cpe:/a:google:chrome:35.0.1916.47
cpe:/a:google:chrome:35.0.1916.48
cpe:/a:google:chrome:35.0.1916.49
cpe:/a:google:chrome:35.0.1916.51
cpe:/a:google:chrome:35.0.1916.52
cpe:/a:google:chrome:35.0.1916.54
cpe:/a:google:chrome:35.0.1916.56
cpe:/a:google:chrome:35.0.1916.57
cpe:/a:google:chrome:35.0.1916.59
cpe:/a:google:chrome:35.0.1916.61
cpe:/a:google:chrome:35.0.1916.68
cpe:/a:google:chrome:35.0.1916.69
cpe:/a:google:chrome:35.0.1916.71
cpe:/a:google:chrome:35.0.1916.72
cpe:/a:google:chrome:35.0.1916.74
cpe:/a:google:chrome:35.0.1916.77
cpe:/a:google:chrome:35.0.1916.80
cpe:/a:google:chrome:35.0.1916.82
cpe:/a:google:chrome:35.0.1916.84
cpe:/a:google:chrome:35.0.1916.85
cpe:/a:google:chrome:35.0.1916.86
cpe:/a:google:chrome:35.0.1916.88
cpe:/a:google:chrome:35.0.1916.90
cpe:/a:google:chrome:35.0.1916.92
cpe:/a:google:chrome:35.0.1916.93
cpe:/a:google:chrome:35.0.1916.95
cpe:/a:google:chrome:35.0.1916.96
cpe:/a:google:chrome:35.0.1916.98
cpe:/a:google:chrome:35.0.1916.99
cpe:/a:google:chrome:35.0.1916.101
cpe:/a:google:chrome:35.0.1916.103
cpe:/a:google:chrome:35.0.1916.104
cpe:/a:google:chrome:35.0.1916.105
cpe:/a:google:chrome:35.0.1916.106
cpe:/a:google:chrome:35.0.1916.107
cpe:/a:google:chrome:35.0.1916.108
cpe:/a:google:chrome:35.0.1916.109
cpe:/a:google:chrome:35.0.1916.110
cpe:/a:google:chrome:35.0.1916.111
cpe:/a:google:chrome:35.0.1916.112
cpe:/a:google:chrome:35.0.1916.113
cpe:/a:google:chrome:35.0.1916.114
cpe:/a:google:chrome:35.0.1916.115
cpe:/a:google:chrome:35.0.1916.116
cpe:/a:google:chrome:35.0.1916.117
cpe:/a:google:chrome:35.0.1916.118
cpe:/a:google:chrome:35.0.1916.119
cpe:/a:google:chrome:35.0.1916.120
cpe:/a:google:chrome:35.0.1916.121
cpe:/a:google:chrome:35.0.1916.122
cpe:/a:google:chrome:35.0.1916.123
cpe:/a:google:chrome:35.0.1916.124
cpe:/a:google:chrome:35.0.1916.125
cpe:/a:google:chrome:35.0.1916.126
cpe:/a:google:chrome:35.0.1916.127
cpe:/a:google:chrome:35.0.1916.128
cpe:/a:google:chrome:35.0.1916.137
cpe:/a:google:chrome:35.0.1916.138
cpe:/a:google:chrome:35.0.1916.140
cpe:/a:google:chrome:35.0.1916.141
cpe:/a:google:chrome:35.0.1916.142
cpe:/a:google:chrome:35.0.1916.149
cpe:/a:google:chrome:35.0.1916.150
cpe:/a:google:chrome:35.0.1916.151
cpe:/a:google:chrome:35.0.1916.152

Date published: 2014-06-11T06:57:18.610-04:00

Date last modified: 2017-01-06T21:59:54.300-05:00

CVSS Score: 7.5

Principal attack vector: NETWORK

Complexity:  LOW

Reference URL: http://googlechromereleases.blogspot.com/2014/06/stable-channel-update.html

Summary: Heap-based buffer overflow in the FFmpegVideoDecoder::GetVideoBuffer function in media/filters/ffmpeg_video_decoder.cc in Google Chrome before 35.0.1916.153 allows remote attackers to cause a denial of service or possibly have unspecified other impact by leveraging VideoFrame data structures that are too small for proper interaction with an underlying FFmpeg library.

CategoriesUncategorised

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.