XAMPP v7.0.13 is containing PHP v7.0.9 instead v7.0.13

[akansh]

XAMPP v7.0.13 is containing PHP v7.0.9 instead v7.0.13. Please advise if there is any plan to resolve this issue, as lots of vulnerabilities are unresolved because of older PHP Version.

[Altrea]

No. Wait for a new XAMPP version.
Btw: Which of the vulnerabilities do you think (from your experts point of view) is relevant in context of a local test and development environment?

[Nobbie]

as lots of vulnerabilities are unresolved because of older PHP Version.

Which? Please tell us. And how does it affect your development environment?

[akansh]

Here is the list --


PHP prior to 7.0.10.

It is, therefore, affected by multiple vulnerabilities :

- An overflow condition exists in the curl_escape() function in interface.c due to improper handling of overly long strings. An unauthenticated, remote attackercan exploit this to cause a heap-based buffer overflow,resulting in a denial of service condition or the execution of arbitrary code. (VulnDB 143095)

- An integer overflow condition exists in the zend_mm_realloc_heap() function in zend_alloc.c due to improper validation of user-supplied input. An unauthenticated, remote attacker can exploit this to cause a buffer overflow, resulting in a denial of service condition or the execution of arbitrary code. (VulnDB 143115)

PHP is prior to 7.0.11.

It is, therefore, affected by multiple vulnerabilities :

- An heap buffer overflow condition exists in the php_mysqlnd_rowp_read_text_protocol_aux() function within file ext/mysqlnd/mysqlnd_wireprotocol.c due to a failure to verify that a BIT field has the UNSIGNED_FLAG flag. An unauthenticated, remote attacker can exploit this, via specially crafted field metadata, to cause a denial of service condition. (CVE-2016-7412)

- A use-after-free error exists in the wddx_stack_destroy() function within file ext/wddx/wddx.c when deserializing recordset elements. An unauthenticated, remote attacker can exploit this, via a specially crafted wddxPacket XML document, to cause a denial of service condition. (CVE-2016-7413)

- An out-of-bounds access error exists in the phar_parse_zipfile() function within file ext/phar/zip.c due to a failure to ensure that the uncompressed_filesize field is large enough. An unauthenticated, remote attacker can exploit this, via a specially crafted archive, to cause a denial of service condition. (CVE-2016-7414)

- A stack-based buffer overflow condition exists in the ICU4C library, specifically within file common/locid.cpp in the the msgfmt_format_message() function, due to a failure to properly restrict the locale length provided to the Locale class. An unauthenticated, remote attacker can exploit this, via a long first argument to a MessageFormatter::formatMessage() function call, to cause a denial of service condition. (CVE-2016-7416)

- A flaw exists in the spl_array_get_dimension_ptr_ptr() function within file ext/spl/spl_array.c due to a failure to properly validate the return value and data type when deserializing SplArray. An unauthenticated, remote attacker can exploit this, via specially crafted serialized data, to cause a denial of service condition. (CVE-2016-7417)

- An out-of-bounds read error exists in the php_wddx_push_element() function within file ext/wddx/wddx.c when handling an incorrect boolean element, which leads to mishandling the wddx_deserialize() call. An unauthenticated, remote attacker can exploit this, via a specially crafted wddxPacket XML document, to cause a denial of service condition. (CVE-2016-7418)

- An out-of-bounds access error exists in the phar_parse_tarfile() function within file ext/phar/tar.c when handling the verification of signatures. An unauthenticated, remote attacker can exploit this to cause an unspecified impact. (VulnDB 144264)


PHP is prior to 7.0.12.

It is, therefore, affected by multiple vulnerabilities :

- A NULL pointer dereference flaw exists in the SimpleXMLElement::asXML() function within file ext/simplexml/simplexml.c. An unauthenticated, remote attacker can exploit this to cause a denial of service condition. (VulnDB 145598)

- A flaw exists in the openssl_random_pseudo_bytes() function within file ext/openssl/openssl.c when handling strings larger than 2GB. An unauthenticated, remote attacker can exploit this to cause a denial of service condition. (VulnDB 145600)

- A flaw exists in the openssl_encrypt() function within file ext/openssl/openssl.c when handling strings larger than 2GB. An unauthenticated, remote attacker can exploit this to cause a denial of service condition. (VulnDB 145601)

- A flaw exists in the _bc_new_num_ex() function within file ext/bcmath/libbcmath/src/init.c when handling values passed via the 'scale' parameter. An unauthenticated, remote attacker can exploit this to cause a denial of service condition. (VulnDB 145603)

- A flaw exists in the php_resolve_path() function within file main/fopen_wrappers.c when handling negative size values passed via the 'filename' parameter. An unauthenticated, remote attacker can exploit this to cause a denial of service condition. (VulnDB 145604)

- A flaw exists in the dom_document_save_html() function within file ext/dom/document.c due to missing NULL checks. An unauthenticated, remote attacker can exploit this to cause a denial of service condition. (VulnDB 145605)

- A use-after-free error exists in the unserialize() function that allows an unauthenticated, remote attacker to dereference already freed memory, resulting in the execution of arbitrary code. (VulnDB 145606)

- An integer overflow condition exists in the number_format() function within file ext/standard/math.c when handling 'decimals' and 'dec_point' parameters that have values that are equal or close to 0x7fffffff. An unauthenticated, remote attacker can exploit this to cause a heap buffer overflow, resulting in a denial of service condition or the execution of arbitrary code. (VulnDB 145609)

- A stack-based overflow condition exists in the ResourceBundle::create and ResourceBundle::getLocales methods and their respective functions within file ext/intl/resourcebundle/resourcebundle_class.c due to improper validation of input passed via the 'bundlename' parameter. An unauthenticated, remote attacker can exploit this to cause a denial of service condition or the execution or arbitrary code. (VulnDB 145610)

- An integer overflow condition exists in the php_pcre_replace_impl() function within file ext/pcre/php_pcre.c due to improper validation of user-supplied input. An unauthenticated, remote attacker can exploit this to cause a heap-based buffer overflow, resulting in a denial of service condition or the execution of arbitrary code. (VulnDB 145611)

- A flaw exists in file ext/date/php_date.c within the php_date_interval_initialize_from_hash() function, when deserializing DateInterval objects, that allows an unauthenticated, remote attacker to cause an unspecified impact. (VulnDB 145613)

- An unspecified flaw exists in the SplObjectStorage::unserialize() function within file ext/spl/spl_observer.c due to allowing the use of non-objects as keys. An unauthenticated, remote attacker can exploit this to cause an unspecified impact. (VulnDB 145614)

PHP is prior to 7.0.13.

It is, therefore, affected by multiple vulnerabilities :

- A flaw exists in the parse_url() function due to returning the incorrect host. An unauthenticated, remote attacker can exploit this to have a multiple impacts depending on how the function is implemented, which can include bypassing authentication or conducting open redirection and server-side request forgery attacks. (VulnDB 145227)

- An integer overflow condition exists in the _php_imap_mail() function in file ext/imap/php_imap.c when handling overly long strings. An unauthenticated, remote attacker can exploit this to cause a heap-based buffer overflow, resulting in a denial of service condition or the execution of arbitrary code. (VulnDB 146957)

- An integer overflow condition exists in the gdImageAALine() function within file ext/gd/libgd/gd.c due to improper validation of line limit values. An unauthenticated, remote attacker can exploit this to cause an out-of-bounds memory read or write, resulting in a denial of service condition, the disclosure of memory contents, or the execution of arbitrary code. (VulnDB 147321)

PHP is prior to 7.0.14.

It is, therefore, affected by a remote code execution vulnerability due to a memory corruption issue in the php_wddx_push_element() function in ext/wddx/wddx.c that occurs when decoding empty boolean elements. An unauthenticated, remote attacker can exploit this to cause a denial of service condition or the execution of arbitrary code.

[Altrea]

I know outputs of vulnerability scanners like Tenable Nessus and i can read the PHP Changelog.
The problem of such scanners is that the people getting such reports (like company staff) often are not able to set these warnings and alerts in the correct context.

Nearly all of the vulnerabilities of PHP are only a security problem if PHP is used as public accessible webserver component. Especially XAMPP but also other preconfigured webserver stacks are NOT meant for such environments.

[akansh]

Dear Altrea ,

Looking for a simpler answer, when is plan to release XAMPP with PHP version v7.0.13(actually) or latest. Please advise. Renaming the current XAMPP download file to v7.0.9 will also help many users, as declaration will be corrected with actually used.

[Altrea]

when is plan to release XAMPP with PHP version v7.0.13(actually) or latest.

I don't know. There is no XAMPP release schedule available. And i am not part of the XAMPP development team.

[Nobbie]

Here is the list --

No, not a boring list of eventualities. See my question, HOW DOES IT AFFECT YOUR DEVELOPMENT?

Please give us a full list of code snippets from YOUR development, which exploits one of these vulnerabilities. Dont forget: Xampp is for your development, it is not running on official Online servers. So what is your personal concern with these vulnerabilities and how do these affect your personal development? What did you have to change in your code and why and how did you change it?

Please show us YOUR problems and the code.

[akansh]

when is plan to release XAMPP with PHP version v7.0.13(actually) or latest.

I don't know. There is no XAMPP release schedule available. And i am not part of the XAMPP development team.

Dear Altrea,
Thanks for share the information in positive way. Lets wait XAMPP development team to answer the question-- "when is plan to release XAMPP with PHP version v7.0.13(actually) or latest."

[akansh]

Dear Nobbie,

Thank you. I didn’t have any specific concern but wanted to point out the discrepancy that website says 7.0.13 and actual version was different.

[Nobbie]

but wanted to point out the discrepancy that website says 7.0.13 and actual version was different.

That is already known since a couple of month, see:

viewtopic.php?f=17&t=74932

or

viewtopic.php?f=17&t=74939

I dont know why Bitnami does not react, but this issue is quite old. Anyway, i dont see a real problem there, it should not influence someones development in any means.