Bug 403441 - (CVE-2007-5497) CVE-2007-5497 e2fsprogs multiple integer overflows
CVE-2007-5497 e2fsprogs multiple integer overflows
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
: Security
Depends On: 414561 414571 414581 414591 414601 414611 414621 414631 414641 414651
  Show dependency treegraph
Reported: 2007-11-28 15:16 EST by Josh Bressers
Modified: 2016-03-04 05:43 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-01-17 05:08:53 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Proposed upstream patch (10.56 KB, patch)
2007-11-28 15:30 EST, Josh Bressers
no flags Details | Diff
Final upstream patch (11.68 KB, patch)
2007-12-07 02:54 EST, Tomas Hoger
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2008:0003 normal SHIPPED_LIVE Moderate: e2fsprogs security update 2008-01-07 13:57:42 EST

  None (edit)
Description Josh Bressers 2007-11-28 15:16:27 EST
Rafal Wojtczuk of McAfee AVERT Research discovered multiple integer overflows in
e2fsprogs.  These flaws could result in the execution of arbitrary code if a
program using libext2fs (e2fsck, dumpe2fs, pygrub) is used to process a
malicious filesystem.

Under normal conditions this practice is not common.  The most plausible attack
would be to leverage this flaw in a virtualized environment to gain access to dom0.


Red Hat would like to thank Rafal Wojtczuk of McAfee Avert Research for responsibly disclosing these issues.
Comment 1 Josh Bressers 2007-11-28 15:30:53 EST
Created attachment 271731 [details]
Proposed upstream patch
Comment 6 Tomas Hoger 2007-12-07 02:54:01 EST
Created attachment 280781 [details]
Final upstream patch

Note You need to log in before you can comment on or make changes to this bug.