Page 10 of 252 results (0.042 seconds)

CVSS: 9.8EPSS: 0%CPEs: 4EXPL: 1

CVE-2017-9226 – oniguruma: Heap buffer overflow in next_state_val() during regular expression compilation

https://notcve.org/view.php?id=CVE-2017-9226

An issue was discovered in Oniguruma 6.2.0, as used in Oniguruma-mod in Ruby through 2.4.1 and mbstring in PHP through 7.1.5. A heap out-of-bounds write or read occurs in next_state_val() during regular expression compilation. Octal numbers larger than 0xff are not handled correctly in fetch_token() and fetch_token_in_cc(). A malformed regular expression containing an octal number in the form of '\700' would produce an invalid code point value larger than 0xff in next_state_val(), resulting in an out-of-bounds write memory corruption. Un problema fue encontrado en Oniguruma versión 6.2.0, tal y como es usado en Oniguruma-mod en Ruby hasta la versión 2.4.1 y mbstring en PHP hasta la versión 7.1.5. • http://www.securityfocus.com/bid/101244 https://access.redhat.com/errata/RHSA-2018:1296 https://github.com/kkos/oniguruma/commit/b4bf968ad52afe14e60a2dc8a95d3555c543353a https://github.com/kkos/oniguruma/commit/f015fbdd95f76438cd86366467bb2b39870dd7c6 https://github.com/kkos/oniguruma/issues/55 https://access.redhat.com/security/cve/CVE-2017-9226 https://bugzilla.redhat.com/show_bug.cgi?id=1466736 • CWE-787: Out-of-bounds Write •

CVSS: 7.5EPSS: 0%CPEs: 6EXPL: 1

CVE-2017-9229 – oniguruma: Invalid pointer dereference in left_adjust_char_head()

https://notcve.org/view.php?id=CVE-2017-9229

An issue was discovered in Oniguruma 6.2.0, as used in Oniguruma-mod in Ruby through 2.4.1 and mbstring in PHP through 7.1.5. A SIGSEGV occurs in left_adjust_char_head() during regular expression compilation. Invalid handling of reg->dmax in forward_search_range() could result in an invalid pointer dereference, normally as an immediate denial-of-service condition. Se descubrió un problema en Oniguruma versión 6.2.0, como es usado en Oniguruma-mod en Ruby hasta versión 2.4.1 y mbstring en PHP hasta versión 7.1.5. Un SIGSEGV se produce en la función left_adjust_char_head() durante la compilación de expresiones regulares. • https://access.redhat.com/errata/RHSA-2018:1296 https://github.com/kkos/oniguruma/commit/b690371bbf97794b4a1d3f295d4fb9a8b05d402d https://github.com/kkos/oniguruma/issues/59 https://access.redhat.com/security/cve/CVE-2017-9229 https://bugzilla.redhat.com/show_bug.cgi?id=1466746 • CWE-476: NULL Pointer Dereference CWE-787: Out-of-bounds Write •

CVSS: 9.8EPSS: 0%CPEs: 2EXPL: 1

CVE-2017-8923

https://notcve.org/view.php?id=CVE-2017-8923

The zend_string_extend function in Zend/zend_string.h in PHP through 7.1.5 does not prevent changes to string objects that result in a negative length, which allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact by leveraging a script's use of .= with a long string. La función zend_string_extend en el archivo Zend/zend_string.h en PHP hasta de la versión 7.1.5 no impide cambios en los objetos de cadena que resultan en una longitud negativa, lo que permite a los atacantes remotos causar una denegación de servicio (bloqueo de aplicación) o posiblemente tener otro impacto no especificado explotando el uso de scripts .= con una cadena larga. • http://www.securityfocus.com/bid/98518 https://bugs.php.net/bug.php?id=74577 • CWE-787: Out-of-bounds Write •

CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0

CVE-2017-7963

https://notcve.org/view.php?id=CVE-2017-7963

The GNU Multiple Precision Arithmetic Library (GMP) interfaces for PHP through 7.1.4 allow attackers to cause a denial of service (memory consumption and application crash) via operations on long strings. NOTE: the vendor disputes this, stating "There is no security issue here, because GMP safely aborts in case of an OOM condition. The only attack vector here is denial of service. However, if you allow attacker-controlled, unbounded allocations you have a DoS vector regardless of GMP's OOM behavior. ** DISPUTADA ** Las interfaces GNU Multiple Precision Arithmetic Library (GMP) para PHP hasta la versión 7.1.4 permiten a atacantes provocar una denegación de servicio (consumo de memoria y caída de aplicación) a través de operaciones en cadenas largas. NOTA: el proveedor se opone a esto, declarando: "No hay ningún problema de seguridad aquí, porque GMP aborta de forma segura en caso de una condición de OOM. • https://bugs.php.net/bug.php?id=74308 • CWE-770: Allocation of Resources Without Limits or Throttling •

CVSS: 7.4EPSS: 0%CPEs: 1EXPL: 0

CVE-2017-7272

https://notcve.org/view.php?id=CVE-2017-7272

PHP through 7.1.11 enables potential SSRF in applications that accept an fsockopen or pfsockopen hostname argument with an expectation that the port number is constrained. Because a :port syntax is recognized, fsockopen will use the port number that is specified in the hostname argument, instead of the port number in the second argument of the function. PHP hasta la versión 7.1.11 podría permitir SSRF en aplicaciones que aceptan un argumento de nombre de host fsockopen o pfsockopen con la expectativa de que el número de puerto esté limitado. Debido a que se reconoce una sintaxis :port, fsockopen empleará el número de puerto especificado en el argumento del nombre de host en lugar del número de puerto en el segundo argumento de la función. • http://www.securityfocus.com/bid/97178 http://www.securitytracker.com/id/1038158 https://bugs.php.net/bug.php?id=74216 https://bugs.php.net/bug.php?id=75505 https://github.com/php/php-src/commit/bab0b99f376dac9170ac81382a5ed526938d595a https://security.netapp.com/advisory/ntap-20180112-0001 https://www.sec-consult.com/fxdata/seccons/prod/temedia/advisories_txt/20170403-0_PHP_Misbehavior_of_fsockopen_function_v10.txt • CWE-918: Server-Side Request Forgery (SSRF) •