Christian Schneider

A security vulnerability has been detected in iomad up to 4.5.15/5.0.11/5.1.8/5.2.4. Affected by this issue is the function store temporary password of the file public/local/iomad/classes/company user.php of the component Password Field Handler. Such manipulation leads to information disclosure. The attack may be performed from remote. The attack requires a high level of complexity. The exploitation is known to be difficult. The name of the patch is 0d9c0ccaa8a77583f5dd92eb7be7fbbb8cc6ec9b/9c740fd254fd12d56d7be3b85ac5e9fb4f8c03d8/33755cdd551a84be423b1eaf784d405c1988dbad/7fcf9b52c539a67f3e46a8da6b42ab1d1f26295b. It is advisable to implement a patch to correct this issue. This CVE was requested by the vendor.

The issue allows remote attackers to execute arbitrary commands via a crafted serialized Java object in an HTTP request.

O Java Message Service (JMS) no broker não restringe as classes que podem ser serializadas, levando a uma desserialização insegura. Esta falta de validação de entrada permite que um invasor remoto execute código arbitrário enviando um objeto `ObjectMessage` serializado especialmente criado.

The issue is related to an absolute path traversal vulnerability in the MapAPI. This allows remote attackers to read arbitrary files.

The issue arises from the failure to verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate. This allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.