Bug 1199103 (CVE-2015-0252)
| Summary: | CVE-2015-0252 xerces-c: crashes on malformed input | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | Vasyl Kaigorodov <vkaigoro> | ||||
| Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> | ||||
| Status: | CLOSED ERRATA | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | unspecified | CC: | antti.andreimann, avagarwa, bhu, bleanhar, ccoleman, dmcphers, erik-fedora, esammons, fweimer, iboverma, jarno.huuskonen, jdetiber, jialiu, jkeck, jokerman, jonathan.robie, jross, jrusnack, kalevlember, kpalko, kseifried, lmeyer, magoldma, matt, mcressma, mmccomas, moremellotron, mrg-program-list, rrajasek, sardella, security-response-team, volker27, williams, xavier | ||||
| Target Milestone: | --- | Keywords: | Security | ||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | xerces-c 3.1.2 | Doc Type: | Bug Fix | ||||
| Doc Text: |
A flaw was found in the way the Xerces-C XML parser processed certain XML documents. A remote attacker could provide specially crafted XML input that, when parsed by an application using Xerces-C, would cause that application to crash.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-06-30 07:21:35 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 1204018, 1204019, 1204020, 1204021, 1217104, 1217105 | ||||||
| Bug Blocks: | 1199109 | ||||||
| Attachments: |
|
||||||
|
Description
Vasyl Kaigorodov
2015-03-05 13:21:33 UTC
Created attachment 998360 [details]
XMLReader.cpp.patch
This is now public: http://seclists.org/oss-sec/2015/q1/892 Upstream commit: http://svn.apache.org/viewvc?view=revision&revision=1667870 External References: http://xerces.apache.org/xerces-c/secadv/CVE-2015-0252.txt Created mingw-xerces-c tracking bugs for this issue: Affects: fedora-all [bug 1204019] Created xerces-c tracking bugs for this issue: Affects: fedora-all [bug 1204018] Affects: epel-6 [bug 1204021] Created xerces-c27 tracking bugs for this issue: Affects: fedora-all [bug 1204020] xerces-c-3.1.2-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. mingw-xerces-c-3.1.2-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. xerces-c-3.1.1-8.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report. mingw-xerces-c-3.1.1-9.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. mingw-xerces-c-3.1.1-11.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report. xerces-c-3.1.1-6.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. Does CVE-2015-0252 affect xerces-c-3.1.1-6.el7.x86_64 that comes with "Red Hat Enterprise Linux Server release 7.1 (Maipo)" ? On RHEL7 shibboleth sp (http://shibboleth.net/products/service-provider.html) uses xerces-c. Fix for CVE-2015-0252 is important because shibboleth sp has DoS vulnerability: https://shibboleth.net/community/advisories/secadv_20150319.txt (In reply to Jarno Huuskonen from comment #15) > Does CVE-2015-0252 affect xerces-c-3.1.1-6.el7.x86_64 that comes with "Red > Hat Enterprise Linux Server release 7.1 (Maipo)" ? > > On RHEL7 shibboleth sp > (http://shibboleth.net/products/service-provider.html) uses xerces-c. Fix > for CVE-2015-0252 is important because shibboleth sp has DoS vulnerability: > https://shibboleth.net/community/advisories/secadv_20150319.txt Upstream states versions prior to 3.1.2 are affected, and RHEL 7.1 version is affected, too. Is there any kind of timeline on this? My community is left hanging, and it's been an unacceptably long period of time to leave a bug this serious unpatched. I did a lot of work to get this fix out there from upstream, when that project was essentially dead, and this isn't really making me feel like it was worth my time. This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2015:1193 https://rhn.redhat.com/errata/RHSA-2015-1193.html Hello Scott, I apologize for the delay - this has been handled unusually long. This issue has been stalled three times in various stages of our process due to extraordinary complications. I am going to do a postmortem now and make sure these are documented and addressed in the future. Thank you ! Thank you for getting the fix out, and for responding. I'm glad that at least this wasn't a routine situation. |