security update available for chromium

Bug #584016 reported by Jamie Strandboge
262
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Fix Released
Undecided
Unassigned
Lucid
Fix Released
Undecided
Fabien Tassin
Maverick
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: chromium-browser

Bug to track verification status of new chromium upstream release.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Marking 'In Progress' per https://wiki.ubuntu.com/SecurityTeam/SponsorsQueue.

Uploaded to ubuntu-security-proposed PPA and it is currently building.

security vulnerability: no → yes
Changed in chromium-browser (Ubuntu Maverick):
status: New → Fix Released
Changed in chromium-browser (Ubuntu Lucid):
status: New → Confirmed
status: Confirmed → In Progress
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Fabien,

Can you detail the changes that were made between Lucid and this release? The changelog is terse and chromium does not have a microrelease exception (yet) so it is going to have to follow the SRU process and be justified for inclusion in Lucid.

Thanks!

Changed in chromium-browser (Ubuntu Lucid):
assignee: nobody → Fabien Tassin (fta)
Revision history for this message
Fabien Tassin (fta) wrote :

It's difficult for me to provide the information you're requesting. This is a huge source tree moving very fast.
I'm currently aligning our releases on the upstream releases of Google Chrome from the Beta Channel and i plan on doing so until there's a Stable Channel for Linux.

Upstream only provides minimal changelogs: http://googlechromereleases.blogspot.com/search/label/Beta%20updates
This is what i re-use in our changelogs (the All+Linux parts only)

I'm attaching some raw data if you're willing to have a closer look.

Revision history for this message
Fabien Tassin (fta) wrote :
Revision history for this message
Fabien Tassin (fta) wrote :
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

We would like to know which of the following issues the update fixes:

http://people.canonical.com/~ubuntu-security/cve/pkg/chromium-browser.html

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

The chromium-browser update currently in the PPA (5.0.375.38~r46659-0ubuntu0.10.04.1) fixes the following issues:

CVE-2010-1234
CVE-2010-1236
CVE-2010-1237
CVE-2010-1500
CVE-2010-1501
CVE-2010-1502
CVE-2010-1503
CVE-2010-1504
CVE-2010-1505
CVE-2010-1506
CVE-2010-1663
CVE-2010-1664

It may also fix CVE-2010-1665, but the upstream bug is private, so we don't know what commits fix it.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Pocket copied chromium-browser to proposed. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Changed in chromium-browser (Ubuntu Lucid):
status: In Progress → Fix Committed
tags: added: verification-needed
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

To ubuntu-sru: if this passes the verification process, please also pocket copy to security. Thanks!

Revision history for this message
Fabien Tassin (fta) wrote :

CVE-2010-1665 has been fixed in trunk 342 r40445, hence it is in the 375 branch. So fixed it is.

Revision history for this message
Fabien Tassin (fta) wrote :

... sorry, i messed up with another bug.
2010-1665 fixed (in webkit) which landed in chromium both in 249r45544 (not important for us) and in 375r45594; hence 5.0.375.38~r46659 has it.

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

@ubuntu-sru: I have installed and tested the updated package on lucid, and it is working fine.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

@ubuntu-sru: I too have installed and tested the updated package on lucid, and it is working fine.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Since the changelog did not reference this but and sru-verification was not subscribed, this didn't end up on the SRU team's reports. I have updated SecurityTeam/SponsorsQueue so this doesn't happen in the future. Marking verification-done and coping to -security.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

$ copy-package.py -vbs lucid-proposed --to-suite=lucid-security chromium-browser
2010-06-07 15:05:40 INFO Creating lockfile: /var/lock/launchpad-copy-package.lock
2010-06-07 15:05:47 INFO FROM: Primary Archive for Ubuntu: lucid-PROPOSED
2010-06-07 15:05:47 INFO TO: Primary Archive for Ubuntu: lucid-SECURITY
...
2010-06-07 15:05:49 INFO 19 packages successfully copied.
Confirm this transaction? [yes, no] yes
2010-06-07 15:05:52 INFO Transaction committed.
2010-06-07 15:05:52 INFO Done.

Changed in chromium-browser (Ubuntu Lucid):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.