-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SGI Security Advisory Title : xfsdump creates files insecurely Number : 20030404-01-P Date : April 10, 2003 Reference: CVE CAN-2003-0173 Reference: SGI BUG 885222 Fixed in : IRIX 6.5.20 (when available) or patches 5059 and 5060 ______________________________________________________________________________ - ----------------------- - --- Issue Specifics --- - ----------------------- It's been reported that xfsdump creates quota information files insecurely, possibly leading to a root exploit by a local user. See: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2003-0173 SGI has investigated the issue and recommends the following steps for neutralizing the exposure. It is HIGHLY RECOMMENDED that these measures be implemented on ALL vulnerable SGI systems. These issues have been corrected with patches and in future releases of IRIX. - -------------- - --- Impact --- - -------------- The xfsdump binary is installed by default on IRIX 6.5 systems as part of eoe.sw.base. To determine the version of IRIX you are running, execute the following command: # /bin/uname -R That will return a result similar to the following: # 6.5 6.5.16f The first number ("6.5") is the release name, the second ("6.5.16f" in this case) is the extended release name. The extended release name is the "version" we refer to throughout this document. - ---------------------------- - --- Temporary Workaround --- - ---------------------------- There is no effective workaround available for these problems if you need to use xfsdump on xfs filesystems with quotas. SGI recommends either upgrading to IRIX 6.5.20 (when available), or installing the appropriate patch from the listing below. - ---------------- - --- Solution --- - ---------------- SGI has provided a series of patches for these vulnerabilities. Our recommendation is to upgrade to IRIX 6.5.20 (when available), or install the appropriate patch. OS Version Vulnerable? Patch # Other Actions ---------- ----------- ------- ------------- IRIX 3.x unknown Note 1 IRIX 4.x unknown Note 1 IRIX 5.x unknown Note 1 IRIX 6.0.x unknown Note 1 IRIX 6.1 unknown Note 1 IRIX 6.2 unknown Note 1 IRIX 6.3 unknown Note 1 IRIX 6.4 unknown Note 1 IRIX 6.5 yes Notes 2 & 3 IRIX 6.5.1 yes Notes 2 & 3 IRIX 6.5.2 yes Notes 2 & 3 IRIX 6.5.3 yes Notes 2 & 3 IRIX 6.5.4 yes Notes 2 & 3 IRIX 6.5.5 yes Notes 2 & 3 IRIX 6.5.6 yes Notes 2 & 3 IRIX 6.5.7 yes Notes 2 & 3 IRIX 6.5.8 yes Notes 2 & 3 IRIX 6.5.9 yes Notes 2 & 3 IRIX 6.5.10 yes Notes 2 & 3 IRIX 6.5.11 yes Notes 2 & 3 IRIX 6.5.12 yes Notes 2 & 3 IRIX 6.5.13 yes Notes 2 & 3 IRIX 6.5.14 yes Notes 2 & 3 IRIX 6.5.15 yes Notes 2 & 3 IRIX 6.5.16m yes 5059 Notes 2 & 4 IRIX 6.5.16f yes 5060 Notes 2 & 4 IRIX 6.5.17m yes 5059 Notes 2 & 4 IRIX 6.5.17f yes 5060 Notes 2 & 4 IRIX 6.5.18m yes 5059 Notes 2 & 4 IRIX 6.5.18f yes 5060 Notes 2 & 4 IRIX 6.5.19m yes 5059 Notes 2 & 4 IRIX 6.5.19f yes 5060 Notes 2 & 4 IRIX 6.5.20 no NOTES 1) This version of the IRIX operating has been retired. Upgrade to an actively supported IRIX operating system. See http://support.sgi.com/ for more information. 2) If you have not received an IRIX 6.5.X CD for IRIX 6.5, contact your SGI Support Provider or URL: http://support.sgi.com/ 3) Upgrade to IRIX 6.5.20 (when available) 4) Upgrade to IRIX 6.5.20 (when available) or install the patch ##### Patch File Checksums #### The actual patch will be a tar file containing the following files: Filename: README.patch.5059 Algorithm #1 (sum -r): 42028 10 README.patch.5059 Algorithm #2 (sum): 2632 10 README.patch.5059 MD5 checksum: 1AC8B7BE35C147D14C6BE8E57BBE3506 Filename: patchSG0005059 Algorithm #1 (sum -r): 35357 4 patchSG0005059 Algorithm #2 (sum): 54133 4 patchSG0005059 MD5 checksum: 95B0D4C4F6EEA7BF3485B2770F979E0A Filename: patchSG0005059.eoe_man Algorithm #1 (sum -r): 40035 6 patchSG0005059.eoe_man Algorithm #2 (sum): 1308 6 patchSG0005059.eoe_man MD5 checksum: 9AF1B72719A03646FEC03FF8C172FB73 Filename: patchSG0005059.eoe_sw Algorithm #1 (sum -r): 29249 359 patchSG0005059.eoe_sw Algorithm #2 (sum): 22794 359 patchSG0005059.eoe_sw MD5 checksum: 3B62950D43457B4F56D50257500FC443 Filename: patchSG0005059.idb Algorithm #1 (sum -r): 59650 2 patchSG0005059.idb Algorithm #2 (sum): 59732 2 patchSG0005059.idb MD5 checksum: FA2044B2B051A7AAA423CC9B816B3E22 Filename: README.patch.5060 Algorithm #1 (sum -r): 33966 10 README.patch.5060 Algorithm #2 (sum): 2418 10 README.patch.5060 MD5 checksum: D543B3BE2BFFE152ECF88ECDFD7A8582 Filename: patchSG0005060 Algorithm #1 (sum -r): 14237 4 patchSG0005060 Algorithm #2 (sum): 59998 4 patchSG0005060 MD5 checksum: 92AFE1F0DDE38503FB48A02CBBE35D80 Filename: patchSG0005060.eoe_man Algorithm #1 (sum -r): 07693 6 patchSG0005060.eoe_man Algorithm #2 (sum): 41147 6 patchSG0005060.eoe_man MD5 checksum: 47A55B469DEAEA18136C7540A01435D5 Filename: patchSG0005060.eoe_sw Algorithm #1 (sum -r): 31162 361 patchSG0005060.eoe_sw Algorithm #2 (sum): 15461 361 patchSG0005060.eoe_sw MD5 checksum: 5ECD41272723A9B80D56AF17265FDDA4 Filename: patchSG0005060.idb Algorithm #1 (sum -r): 28575 2 patchSG0005060.idb Algorithm #2 (sum): 59664 2 patchSG0005060.idb MD5 checksum: D6F4923E4BF2677607A892CFA2101AF7 - ------------------------ - --- Acknowledgments ---- - ------------------------ SGI wishes to thank Ethan Benson, Nathan Scott and Debian for their assistance in this matter. - ------------- - --- Links --- - ------------- SGI Security Advisories can be found at: http://www.sgi.com/support/security/ and ftp://patches.sgi.com/support/free/security/advisories/ SGI Security Patches can be found at: http://www.sgi.com/support/security/ and ftp://patches.sgi.com/support/free/security/patches/ SGI patches for IRIX can be found at the following patch servers: http://support.sgi.com/ and ftp://patches.sgi.com/ SGI freeware updates for IRIX can be found at: http://freeware.sgi.com/ SGI fixes for SGI open sourced code can be found on: http://oss.sgi.com/projects/ SGI patches and RPMs for Linux can be found at: http://support.sgi.com/ or http://oss.sgi.com/projects/sgilinux-combined/download/security-fixes/ SGI patches for Windows NT or 2000 can be found at: http://support.sgi.com/ IRIX 5.2-6.4 Recommended/Required Patch Sets can be found at: http://support.sgi.com/ and ftp://patches.sgi.com/support/patchset/ IRIX 6.5 Maintenance Release Streams can be found at: http://support.sgi.com/ IRIX 6.5 Software Update CDs can be obtained from: http://support.sgi.com/ The primary SGI anonymous FTP site for security advisories and patches is patches.sgi.com. Security advisories and patches are located under the URL ftp://patches.sgi.com/support/free/security/ For security and patch management reasons, ftp.sgi.com (mirrors patches.sgi.com security FTP repository) lags behind and does not do a real-time update. - ----------------------------------------- - --- SGI Security Information/Contacts --- - ----------------------------------------- If there are questions about this document, email can be sent to security-info@sgi.com. ------oOo------ SGI provides security information and patches for use by the entire SGI community. This information is freely available to any person needing the information and is available via anonymous FTP and the Web. The primary SGI anonymous FTP site for security advisories and patches is patches.sgi.com. Security advisories and patches are located under the URL ftp://patches.sgi.com/support/free/security/ The SGI Security Headquarters Web page is accessible at the URL: http://www.sgi.com/support/security/ For issues with the patches on the FTP sites, email can be sent to security-info@sgi.com. For assistance obtaining or working with security patches, please contact your SGI support provider. ------oOo------ SGI provides a free security mailing list service called wiretap and encourages interested parties to self-subscribe to receive (via email) all SGI Security Advisories when they are released. Subscribing to the mailing list can be done via the Web (http://www.sgi.com/support/security/wiretap.html) or by sending email to SGI as outlined below. % mail wiretap-request@sgi.com subscribe wiretap <YourEmailAddress such as aaanalyst@sgi.com > end ^d In the example above, <YourEmailAddress> is the email address that you wish the mailing list information sent to. The word end must be on a separate line to indicate the end of the body of the message. The control-d (^d) is used to indicate to the mail program that you are finished composing the mail message. ------oOo------ SGI provides a comprehensive customer World Wide Web site. This site is located at http://www.sgi.com/support/security/ . ------oOo------ If there are general security questions on SGI systems, email can be sent to security-info@sgi.com. For reporting *NEW* SGI security issues, email can be sent to security-alert@sgi.com or contact your SGI support provider. A support contract is not required for submitting a security report. ______________________________________________________________________________ This information is provided freely to all interested parties and may be redistributed provided that it is not altered in any way, SGI is appropriately credited and the document retains and includes its valid PGP signature. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBPpWf6LQ4cFApAP75AQGtTQQAhastm5/DlpwqIgeJRANYZUi54JERjBmj MZU+mP768cvUz1/13De/qT6j7IbpoH5dlngcGIcMBWycCY6A0oOjEP3gx0jXhf/u CR6FkfzmH7/Eg/QYMqyWaH3Aeugqmr1Qg0vZ9JT2pvQFsEiRqUJSmVcqcCpnEn0B rRw+Yh4pLwg= =ABnC -----END PGP SIGNATURE-----
Can anybody confirm or debunk this one, As far as I can tell were not SGI and this report makes no reference to anything other than SGI's xfsdump being vuln. currently sys-fs/xfsdump-2.2.4-r1 is what we have in portage.
i just added xfsprogs-2.6.3 and xfsdump-2.2.16 to portage to unstable
xfsdump 2.2.16 appears to have the appropriate fix - can we get SpanKY's ebuild tested and marked stable on the various archs? *added x86, ppc, sparc, mips, amd64, ia64
x86 stable now
most of us just got xfs support in 2.4.25 or 2.6.x and probably don't even have xfsprogs keyworded, so this might be a bit (or at least for sparc).
xfsdump-2.2.16 dies on sparc with the following; gcc -mcpu=ultrasparc -O2 -pipe -fPIC -mcpu=ultrasparc -O2 -pipe -fPIC -DNDEBUG -funsigned-char -Wall -I./include -DVERSION=\"2.2.16\" -DLOCALEDIR=\"/usr/share/locale\" -DPACKAGE=\"xfsdump\" -DXFS_BIG_FILES=1 -DXFS_BIG_FILESYSTEMS=1 -mcpu=ultrasparc -O2 -pipe -fPIC -DNDEBUG -funsigned-char -Wall -I../include -DVERSION=\"2.2.16\" -DLOCALEDIR=\"/usr/share/locale\" -DPACKAGE=\"xfsdump\" -DXFS_BIG_FILES=1 -DXFS_BIG_FILESYSTEMS=1 -c -o xfs_estimate.o xfs_estimate.c distcc[17216] ERROR: compile on localhost failed xfs_estimate.c:61: warning: `struct FTW' declared inside parameter list xfs_estimate.c:61: warning: its scope is only this definition or declaration, which is probably not what you want xfs_estimate.c:61: warning: `struct stat64' declared inside parameter list xfs_estimate.c: In function `usage': xfs_estimate.c:99: warning: implicit declaration of function `basename' xfs_estimate.c:99: warning: format argument is not a pointer (arg 3) xfs_estimate.c: In function `main': xfs_estimate.c:156: warning: format argument is not a pointer (arg 2) xfs_estimate.c:183: warning: implicit declaration of function `nftw64' xfs_estimate.c:183: `FTW_PHYS' undeclared (first use in this function) xfs_estimate.c:183: (Each undeclared identifier is reported only once xfs_estimate.c:183: for each function it appears in.) xfs_estimate.c:183: `FTW_MOUNT' undeclared (first use in this function) xfs_estimate.c: At top level: xfs_estimate.c:229: warning: `struct FTW' declared inside parameter list xfs_estimate.c:229: warning: `struct stat64' declared inside parameter list xfs_estimate.c:230: conflicting types for `ffn' xfs_estimate.c:61: previous declaration of `ffn' xfs_estimate.c: In function `ffn': xfs_estimate.c:234: dereferencing pointer to incomplete type xfs_estimate.c:236: dereferencing pointer to incomplete type xfs_estimate.c:237: dereferencing pointer to incomplete type xfs_estimate.c:237: dereferencing pointer to incomplete type xfs_estimate.c:242: dereferencing pointer to incomplete type xfs_estimate.c:243: dereferencing pointer to incomplete type xfs_estimate.c:248: dereferencing pointer to incomplete type make[1]: *** [xfs_estimate.o] Error 1 make: *** [default] Error 2
everyone on the cc list has ~arch in the KEYWORDS how it got there, i dunno, but if it shouldnt be there, one option is to just remove your respective arch from all the versions of xfsdump
XFS has been supported on ppc since ppc-sources-dev-2.4.22 iirc. Darkspecter tests it regulary. So it is known to work on ppc at least.
I adjusted the xfsdump-2.2.16 ebuild so it can build on sparc64. However, it appears at this time that xfsdump won't work due to ioctl issues when using a 64 bit kernel and a 32 but userland, http://oss.sgi.com/bugzilla/show_bug.cgi?id=298 talks more about this. So for now I've masked this on sparc. It's possible xfsdump may work on sparc32, but to my knowledge, no one has tried to build xfs support in a kernel, let alone made one and tested xfsprogs on sparc32. I will attempt it when I return home in the beginning of March (unless someone beats me to it).
xfs builds and insmods on 2.6.3 for sparc32. I have no idea whether it works but there's no good reason it shouldn't.
all set on alpha and ia64, removing from list
mips, amd64 ?
Would someone test 2.2.16 on mips and amd64? I would like to get this year old bug closed. *amd64@gentoo.org removed by mistake & re-added
Done. Removing amd64 from CC
I just tried on mips, but xfsprogs-2.6.3 fails to build on mips. PPC seems to have the same bug issue, see Bug #42181.
all supported arches have marked bug as stable. closing.
mips stable long ago.