Lyris Technologies INC
Lyris Technologies INC Listmanager: vulnerabilidades y CVE
Lyris Technologies INC Listmanager tiene 6 vulnerabilidades publicadas, 0 de ellas en los últimos 12 meses. 0 son críticas y 0 figuran en el catálogo de explotación activa de CISA.
CVE6
Últimos 12 meses0
Críticas0
Explotadas activamente0
Todas las vulnerabilidades en el catálogo →⭐ Seguir esta tecnología
Últimas vulnerabilidades
| CVE | Severidad | EPSS | Explotación activa | Publicada | Descripción |
|---|---|---|---|---|---|
| CVE-2005-4145 | Media (6.5) | 44% | — | 10 dic 2005 | The MSDE version of Lyris ListManager 5.0 through 8.9b configures the sa account in the database to use a password with a small search space ("lyris" and up to 5 digits, possibly from the process ID), which allows… |
| CVE-2005-4146 | Media (5) | 1.6% | — | 10 dic 2005 | Lyris ListManager before 8.9b allows remote attackers to obtain sensitive information via a request to the TCLHTTPd status module, which provides sensitive server configuration information. |
| CVE-2005-4148 | Media (5) | 1.8% | — | 10 dic 2005 | Lyris ListManager 8.5, and possibly other versions before 8.8, includes sensitive information in the env hidden variable, which allows remote attackers to obtain information such as the installation path by requesting a… |
| CVE-2005-4142 | Alta (7.5) | 3.0% | — | 10 dic 2005 | The web interface for subscribing new users in Lyris ListManager 5.0 through 8.8b, in combination with a line wrap feature, allows remote attackers to execute arbitrary list administration commands via LFCR (%0A%0D)… |
| CVE-2005-4149 | Media (5) | 1.4% | — | 10 dic 2005 | Lyris ListManager 8.8 through 8.9b allows remote attackers to obtain sensitive information by causing errors in TML scripts, such as via direct requests, which leaks the installation path, SQL queries, or product code… |
| CVE-2005-4147 | Media (6.5) | 1.9% | — | 10 dic 2005 | The TCLHTTPd service in Lyris ListManager before 8.9b allows remote attackers to obtain source code for arbitrary .tml (TCL) files via (1) a request with a trailing null byte (%00), which might also require (2) an… |