Page 3 of 21 results (0.007 seconds)

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

An issue was discovered in CHICKEN Scheme through 4.12.0. When using a nonstandard CHICKEN-specific extension to allocate an SRFI-4 vector in unmanaged memory, the vector size would be used in unsanitised form as an argument to malloc(). With an unexpected size, the impact may have been a segfault or buffer overflow. Se ha descubierto un problema en CHICKEN Scheme hasta la versión 4.12.0. Cuando se utiliza una extensión CHICKEN-specific no estándar para ubicar un vector SRFI-4 en memoria no administrada, el tamaño del vector se usaría de forma no analizada como un argumento a malloc(). • http://lists.gnu.org/archive/html/chicken-announce/2017-03/msg00000.html http://www.securityfocus.com/bid/97317 • CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer •

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

The "http-client" egg always used a HTTP_PROXY environment variable to determine whether HTTP traffic should be routed via a proxy, even when running as a CGI process. Under several web servers this would mean a user-supplied "Proxy" header could allow an attacker to direct all HTTP requests through a proxy (also known as a "httpoxy" attack). This affects all versions of http-client before 0.10. El huevo "http-client" siempre utilizó una variable de entorno HTTP_PROXY para determinar si el tráfico HTTP debería ser enrutado a través de un proxy, incluso cuando se ejecuta como un proceso CGI. Bajo varios servidores web esto significaría que una cabecera "Proxy" proporcionada por el usuario podría permitir a un atacante dirigir todas las peticiones HTTP a través de un proxy (también conocido como un ataque "httpoxy"). • http://lists.gnu.org/archive/html/chicken-announce/2016-07/msg00000.html http://www.securityfocus.com/bid/92105 • CWE-19: Data Processing Errors •

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

The "process-execute" and "process-spawn" procedures did not free memory correctly when the execve() call failed, resulting in a memory leak. This could be abused by an attacker to cause resource exhaustion or a denial of service. This affects all releases of CHICKEN up to and including 4.11 (it will be fixed in 4.12 and 5.0, which are not yet released). Los procedimientos "process-execute" y "process-spawn" no liberan correctamente la memoria cuando falla la llamada execve(), resultando en una perdida de memoria. Esto podría ser aprovechado por un atacante para provocar un agotamiento de recursos o una denegación de servicio. • http://lists.nongnu.org/archive/html/chicken-announce/2016-08/msg00001.html http://www.securityfocus.com/bid/92550 • CWE-400: Uncontrolled Resource Consumption •

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

The "spiffy-cgi-handlers" egg would convert a nonexistent "Proxy" header to the HTTP_PROXY environment variable, which would allow attackers to direct CGI programs which use this environment variable to use an attacker-specified HTTP proxy server (also known as a "httpoxy" attack). This affects all versions of spiffy-cgi-handlers before 0.5. El huevo "spiffy-cgi-handlers" convertiría una cabecera "Proxy" inexistente a la variable de entorno HTTP_PROXY, lo que podrían permitir a atacantes dirigir programas CGI que usan esta variable de entorno, para utilizar un servidor proxy HTTP especificado por el atacante (también conocido como ataque "httpoxy"). Esto afecta a todas las versiones de spiffy-cgi-handlers anteriores a 0.5. • http://lists.gnu.org/archive/html/chicken-announce/2016-07/msg00000.html http://www.securityfocus.com/bid/92105 • CWE-19: Data Processing Errors •

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

The "process-execute" and "process-spawn" procedures in CHICKEN Scheme used fixed-size buffers for holding the arguments and environment variables to use in its execve() call. This would allow user-supplied argument/environment variable lists to trigger a buffer overrun. This affects all releases of CHICKEN up to and including 4.11 (it will be fixed in 4.12 and 5.0, which are not yet released). Los procedimientos "process-execute" y "process-spawn" en CHICKEN Scheme utilizaron búfers de tamaño fijo para mantener los argumentos y las variables de entorno para usar en su llamada execve(). Esto podría permitir que las listas de variable de argumento/entorno suministradas por el usuario desencadenaran un desbordamiento de búfer. • http://lists.nongnu.org/archive/html/chicken-announce/2016-08/msg00001.html http://www.securityfocus.com/bid/92550 • CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer •