Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 347625 - <www-client/chromium-8.0.552.215: multiple vulnerabilities (CVE-2010-{4482,4483,4484,4485,4486,4487,4488,4489,4490,4491,4492,4493})
Summary: <www-client/chromium-8.0.552.215: multiple vulnerabilities (CVE-2010-{4482,44...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Security
Classification: Unclassified
Component: Vulnerabilities (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Security
URL: http://googlechromereleases.blogspot....
Whiteboard: B2 [glsa]
Keywords:
Depends on: CVE-2010-3429 347481 347676
Blocks:
  Show dependency tree
 
Reported: 2010-12-03 07:53 UTC by Paweł Hajdan, Jr. (RETIRED)
Modified: 2012-09-11 00:16 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paweł Hajdan, Jr. (RETIRED) gentoo-dev 2010-12-03 07:53:19 UTC
See the release notes: http://googlechromereleases.blogspot.com/2010/12/stable-beta-channel-updates.html

Impact:

A remote attacker could entice a user to install a specially crafted extension that would trigger an exploitable crash, leading to an execution of arbitrary code, or Denial of Service.

A remote attacker could entice a user to visit a specially crafted web page that would trigger one of the vulnerabilities, leading to an execution of arbitrary code within the confines of the sandbox, information leak, or a Denial of Service.

Arches, please stabilize:

=www-client/chromium-8.0.552.215

You probably also need to stabilize:

>=media-video/ffmpeg-0.6_p25423
Comment 1 Christian Faulhammer (RETIRED) gentoo-dev 2010-12-03 10:30:40 UTC
(In reply to comment #0)
> You probably also need to stabilize:
> 
> >=media-video/ffmpeg-0.6_p25423

 media-video, is this ok?
Comment 2 Agostino Sarubbo gentoo-dev 2010-12-03 10:55:14 UTC
also pulled in:

=media-sound/lame-3.98.4

sound herd ok?

Comment 3 Alexis Ballier gentoo-dev 2010-12-03 13:47:36 UTC
(In reply to comment #1)
> (In reply to comment #0)
> > You probably also need to stabilize:
> > 
> > >=media-video/ffmpeg-0.6_p25423
> 
>  media-video, is this ok?
> 

yes, see bug #339036
there should be a tinderbox check for the stable tree though
Comment 4 Alexis Ballier gentoo-dev 2010-12-03 13:50:59 UTC
(In reply to comment #3)
> (In reply to comment #1)
> > (In reply to comment #0)
> > > You probably also need to stabilize:
> > > 
> > > >=media-video/ffmpeg-0.6_p25423
> > 
> >  media-video, is this ok?
> > 
> 
> yes, see bug #339036
> there should be a tinderbox check for the stable tree though
> 

there are two versions matching, you should go for 0.6_p25767 btw
Comment 5 Christian Faulhammer (RETIRED) gentoo-dev 2010-12-03 19:43:48 UTC
(In reply to comment #3)
> (In reply to comment #1)
> > (In reply to comment #0)
> > > You probably also need to stabilize:
> > > 
> > > >=media-video/ffmpeg-0.6_p25423
> > 
> >  media-video, is this ok?
> > 
> 
> yes, see bug #339036
> there should be a tinderbox check for the stable tree though

 _p25767 is younger than 30 days, but we can do it nonetheless. Ran a tinderbox on x86 with above patch level, will do again with the newer snapshot no.  Two fixable failures.

Comment 6 Richard Freeman gentoo-dev 2010-12-04 14:04:03 UTC
(In reply to comment #5)
>  _p25767 is younger than 30 days, but we can do it nonetheless. Ran a tinderbox
> on x86 with above patch level, will do again with the newer snapshot no.  Two
> fixable failures.
> 

note that p25767 requires stabilizing =media-libs/x264-0.0.20101029
Comment 7 Christian Faulhammer (RETIRED) gentoo-dev 2010-12-06 11:59:14 UTC
(In reply to comment #6)
> (In reply to comment #5)
> >  _p25767 is younger than 30 days, but we can do it nonetheless. Ran a tinderbox
> > on x86 with above patch level, will do again with the newer snapshot no.  Two
> > fixable failures.
> > 
> 
> note that p25767 requires stabilizing =media-libs/x264-0.0.20101029

 and x264-encoder in the same version.
> 

Comment 8 Christian Faulhammer (RETIRED) gentoo-dev 2010-12-09 08:46:10 UTC
stable x86, those ffmpeg blockers are old and no reaction from maintainers so far
Comment 9 Richard Freeman gentoo-dev 2010-12-09 16:14:22 UTC
amd64 stable
Comment 10 Tim Sammut (RETIRED) gentoo-dev 2010-12-09 18:29:25 UTC
Thanks, folks.

Would it be possible to create an updated www-client/chromium-bin too?
Comment 11 Paweł Hajdan, Jr. (RETIRED) gentoo-dev 2010-12-13 20:58:42 UTC
(In reply to comment #10)
> Would it be possible to create an updated www-client/chromium-bin too?

Sure, I will handle that as part of bug #348651.
Comment 12 Tim Sammut (RETIRED) gentoo-dev 2010-12-14 15:42:58 UTC
=www-client/chromium-bin-8.0.552.224 added via bug 348651.

GLSA with 325451 (and others). Thanks folks.
Comment 13 Tobias Heinlein (RETIRED) gentoo-dev 2010-12-18 00:07:02 UTC
GLSA 201012-01, thanks everyone.
Comment 14 GLSAMaker/CVETool Bot gentoo-dev 2012-09-11 00:16:32 UTC
CVE-2010-4493 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-4493):
  Use-after-free vulnerability in Google Chrome before 8.0.552.215 allows
  remote attackers to cause a denial of service via vectors related to the
  handling of mouse dragging events.

CVE-2010-4492 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-4492):
  Use-after-free vulnerability in Google Chrome before 8.0.552.215 allows
  remote attackers to cause a denial of service or possibly have unspecified
  other impact via vectors involving SVG animations.

CVE-2010-4491 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-4491):
  Google Chrome before 8.0.552.215 does not properly restrict privileged
  extensions, which allows remote attackers to cause a denial of service
  (memory corruption) via a crafted extension.

CVE-2010-4490 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-4490):
  Google Chrome before 8.0.552.215 allows remote attackers to cause a denial
  of service (application crash) or possibly have unspecified other impact via
  malformed video content that triggers an indexing error.

CVE-2010-4489 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-4489):
  libvpx, as used in Google Chrome before 8.0.552.215 and possibly other
  products, allows remote attackers to cause a denial of service
  (out-of-bounds read) via a crafted WebM video.  NOTE: this vulnerability
  exists because of a regression.

CVE-2010-4488 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-4488):
  Google Chrome before 8.0.552.215 does not properly handle HTTP proxy
  authentication, which allows remote attackers to cause a denial of service
  (application crash) via unspecified vectors.

CVE-2010-4487 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-4487):
  Incomplete blacklist vulnerability in Google Chrome before 8.0.552.215 on
  Linux and Mac OS X allows remote attackers to have an unspecified impact via
  a "dangerous file."

CVE-2010-4486 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-4486):
  Use-after-free vulnerability in Google Chrome before 8.0.552.215 allows
  remote attackers to cause a denial of service or possibly have unspecified
  other impact via vectors related to history handling.

CVE-2010-4485 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-4485):
  Google Chrome before 8.0.552.215 does not properly restrict the generation
  of file dialogs, which allows remote attackers to cause a denial of service
  (reduced usability and possible application crash) via a crafted web site.

CVE-2010-4484 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-4484):
  Google Chrome before 8.0.552.215 does not properly handle HTML5 databases,
  which allows attackers to cause a denial of service (application crash) via
  unspecified vectors.

CVE-2010-4483 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-4483):
  Google Chrome before 8.0.552.215 does not properly restrict read access to
  videos derived from CANVAS elements, which allows remote attackers to bypass
  the Same Origin Policy and obtain potentially sensitive video data via a
  crafted web site.

CVE-2010-4482 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-4482):
  Unspecified vulnerability in Google Chrome before 8.0.552.215 allows remote
  attackers to bypass the pop-up blocker via unknown vectors.