Red Hat Bugzilla – Bug 505355
Reference counting bug in SoapClient::__setSoapHeaders()
Last modified: 2011-05-04 05:40:53 EDT
SoapClient :: __setSoapHeaders does not correctly set refcount for the header when there is only a single header object passed. Due to this, a later __soapCall() fails with a segmentation fault since the header has been freed due to its refcount being zero.
Relevant upstream bugzilla:
This was fixed by:
Created attachment 347429 [details]
Reproducer built using sample from
The script will not successfully run since the locations used in the sample script are all bogus. However this does demonstrate the problem clearly.
PHP Fatal error: Uncaught SoapFault exception: [HTTP] Could not connect to host in /root/test.php:20
#0 [internal function]: SoapClient->__doRequest('<?xml version="...', 'http://localhos...', 'http://test-uri...', 1, 0)
#1 /root/test.php(20): SoapClient->__soapCall('echoVoid', Array)
#2 /root/test.php(28): myclass->someOtherMethod()
thrown in /root/test.php on line 20
I've made test packages available which should fix this issue. These
packages are unsupported, have not been through the standard Red Hat
QA process, and are not recommended for use on production systems.
Use of these packages may prevent you from (automatically) upgrading
to any asynchronous security errata which are issued before the
release of RHEL 5.5 due to version mismatches.
Please record any feedback on use of these test packages (positive or
negative!) on this bug report.
~~ Attention Customers and Partners - RHEL 5.5 Beta is now available on RHN ~~
RHEL 5.5 Beta has been released! There should be a fix present in this
release that addresses your request. Please test and report back results
here, by March 3rd 2010 (2010-03-03) or sooner.
Upon successful verification of this request, post your results and update
the Verified field in Bugzilla with the appropriate value.
If you encounter any issues while testing, please describe them and set
this bug into NEED_INFO. If you encounter new defects or have additional
patch(es) to request for inclusion, please clone this bug per each request
and escalate through your support representative.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.