Bug 741022
Summary: | php: changes to is_a() in 5.3.7 may allow arbitrary code execution with certain code [fedora-all] | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Vincent Danen <vdanen> |
Component: | php | Assignee: | Joe Orton <jorton> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 15 | CC: | fedora, jorton, rpm |
Target Milestone: | --- | Keywords: | Security, SecurityTracking |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Release Note | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-06-05 09:41:33 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: | |||
Bug Blocks: | 741020 |
Description
Vincent Danen
2011-09-24 13:52:04 UTC
For security, I think this is a very low risk, as I don't think any application use an _autoload feature without any check on input. As the revert to php <= 5.3.6 of is_a() behaviour is an (late and hardly discussed) upstream decision, and lot of other projects are really hostile to this change, I think we can include this in a 5.3.8 update in fedora. Some other distro choose to not publish php 5.3.8 because of this. @Joe, your thought ? My thoughts: what a mess. You were right to be cautious about this change! It looks like the change to revert to the old is_a behaviour has been committed upstream to the 5.3 branch (r317183) so I don't see a problem with pushing that fix in Fedora updates. I presume that commit alone is sufficient to fix this issue? http://svn.php.net/viewvc?view=revision&revision=317183 Yes this single patch is enough. I will do it |