Vincent Danen

O problema está relacionado a um mecanismo de atualização de plug-ins inseguro, o que poderia permitir que invasores remotos realizassem ataques man-in-the-middle e executassem código arbitrário com as permissões do usuário que está executando o software.

A vulnerabilidade permite que usuários locais obtenham informações confidenciais ao ler o log quando o registro de auditoria está habilitado. Isso ocorre porque a senha do Directory Manager (`nsslapd-rootpw`) é registrada em texto simples ao alterar `cn=config:nsslapd-rootpw`.

**Nome do software vulnerável e versões afetadas: Versões do Symfony 2.0.X a 2.3.X anteriores às versões 2.0.24, 2.1.12, 2.2.5 e 2.3.3 Versão 2.0.X do Symfony anterior à versão 2.0.24 Versão 2.1.X do Symfony anterior à 2.1.12 Versão 2.2.X do Symfony anterior à 2.2.5 Versão 2.3.X do Symfony anterior à 2.3.3 No entanto, para seguir as instruções e consolidar os intervalos na forma mais concisa, o texto acima pode ser simplificado para: Versões 2.0.X a 2.3.X do Symfony anteriores às respectivas versões 2.0.24, 2.1.12, 2.2.5 e 2.3.3 Descrição: A vulnerabilidade reside no componente HttpFoundation, onde o cabeçalho Host pode ser manipulado por um invasor quando a estrutura está gerando uma URL absoluta. Um invasor remoto poderia explorar isso para injetar conteúdo malicioso na página do aplicativo web e realizar vários ataques. Recomendações: Para a versão 2.0.X do Symfony, atualize para a versão 2.0.24 ou posterior. Para a versão 2.1.X do Symfony, atualize para a versão 2.1.12 ou posterior. Para a versão 2.2.X do Symfony, atualize para a versão 2.2.5 ou posterior. Para a versão 2.3.X do Symfony, atualize para a versão 2.3.3 ou posterior.

A security issue was reported, but the patch applied to version 0.0.3-6.fc18 was improper and did not fix the issue.

The issue arises when a new wireless network is created with WPA/WPA2 security in AdHoc mode, resulting in the creation of an open or insecure network.

The issue is related to the suid helper in ecryptfs-utils, which does not properly restrict mounting filesystems with nosuid and nodev options. This oversight creates a possible privilege escalation scenario.

A security bypass issue exists due to a weak encryption error when generating Diffie-Hellman values and RSA keys. This affects the generation of secure keys, potentially compromising the encryption.

The issue is related to the creation of world-writable pid files in /var/run by mom. This could potentially allow unauthorized access or modification of these files.

The issue affects the /webtools/control/xmlrpc endpoint in the OFBiz XML-RPC event handler, making it vulnerable to External Entity Injection. This is achieved by passing DOCTYPE declarations with executable payloads, which can disclose the contents of files in the filesystem. Additionally, it can be used to probe for open network ports and determine whether a file exists or not based on returned error messages.

The issue arises from improper server identity verification before transmitting credential-containing cookies.

The issue concerns a cookie jar in the surf application that has read access from other local users.

The issue is related to a denial of service vulnerability that occurs when parsing #iferror magic functions.

The issue allows execution of arbitrary IRC commands by passing a specially crafted argument to the 'privmsg' handler, potentially causing the client to disconnect from the server. This can be achieved by including carriage returns and line feeds in the argument, such as "some textrQUIT".

The issue allows extremely long passwords to crash Keystone by exhausting stack space.

The issue occurs when a large message is sent and the Digest-MD5 mechanism with a security layer is in use, causing qpid-cpp to crash.

The issue allows attackers to cause a denial of service via a crafted search query, resulting in a NULL pointer dereference. This is due to a problem in the ` ger parse control` function.

The issue is related to an insecure temporary file vulnerability. It is associated with the /tmp/redis.ds file in Redis.

The issue concerns the loss of information during serialization when using the Validator component with caching enabled, specifically with `SymfonyComponentValidatorMappingCacheApcCache` or any other cache implementing `SymfonyComponentValidatorMappingCacheCacheInterface`. This results in the loss of the `collectionCascaded` and `collectionCascadedDeeply` fields. As a consequence, arrays or traversable objects stored in fields using the `@Valid` constraint are not traversed by the validator once the validator configuration is loaded from the cache.

The issue is related to Bitlbee not dropping extra group privileges correctly in the unix.c file. This could potentially lead to security problems, although specific details about exploitation or affected devices are not provided.

The issue allows deleted text to be exposed.