3 ms·

The Chrome Release blog says it's fixed: http://googlechromereleases.blogspot.com/2012/03/chrome-stable-channel-update.html http://googlechromereleases.blogspot

by semenko 15y ago

The Chrome Release blog says it's fixed: http://googlechromereleases.blogspot.com/2012/03/chrome-stable-channel-update.html http://googlechromereleases.blogspot.com/2012/03/chrome-stab... And that the SVN commit history is available: http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog.html?url=/branches/963/src&range=125577:124982&mode=html http://build.chromium.org/f/chromium/perf/dashboard/ui/chang... But I don't see any commit that look even remotely related to this exploit. What's up?

palish 15y ago
Well... They would hopefully be smarter than committing the fix to the public SVN. By committing the fix, they would effectively be releasing a step-by-step guide on how to exploit the vulnerability.
- semenko 15y ago
  But it's still an open source project -- perhaps the commits are more evident in their git repo? http://git.chromium.org/gitweb/ http://git.chromium.org/gitweb/ Certainly if you build Chromium from git/SVN now, the bug is fixed. I just find it a little strange that their changelog / list of commits in each version is not true.
  - silon4 15y ago
    If it's a flash problem, I don't think Chromium has flash at all.
    - bishamon 15y ago
      As the original article points out, this is not a flash related issue.
jamesr 15y ago
The commits are all there, the fixes just might not look completely obvious. We (chromium) commit all fixes to the chromium repository before pushing them to users, always.
- vinhboy 15y ago
  Do you guys ever do write-ups about the bugs? I would be interested in reading that.
  - jamesr 15y ago
    I don't think we do that as a general habit, but that may happen in this case.
emmelaich 15y ago
My wild-arsed guess is: http://src.chromium.org/viewvc/chrome/branches/963/src/content/public/common/url_constants.cc?r1=125576&r2=125575&pathrev=125576 http://src.chromium.org/viewvc/chrome/branches/963/src/conte... -- a change to kUnreachableWebDataURL

by semenko 15y ago

palish 15y ago

Well... They would hopefully be smarter than committing the fix to the public SVN. By committing the fix, they would effectively be releasing a step-by-step guide on how to exploit the vulnerability.

semenko 15y ago
But it's still an open source project -- perhaps the commits are more evident in their git repo? http://git.chromium.org/gitweb/ http://git.chromium.org/gitweb/ Certainly if you build Chromium from git/SVN now, the bug is fixed. I just find it a little strange that their changelog / list of commits in each version is not true.
- silon4 15y ago
  If it's a flash problem, I don't think Chromium has flash at all.
  - bishamon 15y ago
    As the original article points out, this is not a flash related issue.

jamesr 15y ago

The commits are all there, the fixes just might not look completely obvious. We (chromium) commit all fixes to the chromium repository before pushing them to users, always.

vinhboy 15y ago
Do you guys ever do write-ups about the bugs? I would be interested in reading that.
- jamesr 15y ago
  I don't think we do that as a general habit, but that may happen in this case.

emmelaich 15y ago

My wild-arsed guess is: http://src.chromium.org/viewvc/chrome/branches/963/src/content/public/common/url_constants.cc?r1=125576&r2=125575&pathrev=125576 http://src.chromium.org/viewvc/chrome/branches/963/src/conte... -- a change to kUnreachableWebDataURL