Date reported |
Date fixed |
Problem |
Versions |
Risk |
Solution |
January 24, 2008 |
January 22, 2008 |
Three different vulnerabilities | prior to 2.7.1 | Medium | Upgrade to version 2.7.1 | Multiple vulnerabilities have been identified in ELOG, which could be exploited by attackers to execute arbitrary scripting code, cause a denial of service or compromise a vulnerable system.
The first issue is caused by a buffer overflow error in "elog.c" when processing malformed data, which could be exploited to crash an affected application or execute arbitrary code.
The second vulnerability is caused by an infinite loop in the "replace_inline_img()" [elogd.c] function, which could be exploited to crash an affected application.
The third issue is caused by an input validation error when handling the "subtext" parameter, which could be exploited by attackers to cause arbitrary scripting code to be executed by the administrators's browser in the security context of an affected Web site. |
January 19, 2006 |
January 19, 2006 |
Special HTTP requests can disclose the contents of abritrary files on server | prior to 2.6.1 | Critical | Upgrade to version 2.6.1 | Two vulnerabilities were identified in ELOG, which could be exploited by remote attackers to execute arbitrary commands or cause a denial of service.
The first issue is due to a format string error in the "write_logfile()" [elogd.c] function that does not properly handle a specially crafted username, which could be exploited by unauthenticated remote attackers to crash or compromise a vulnerable system.
The second vulnerability is due to an input validation error when processing specially crafted HTTP requests containing directory traversal sequences, which could be exploited by remote attackers to disclose the contents of arbitrary files present on a vulnerable system.
The third vulnerability is due to an error in the "elogd.c" file that does not properly handle overly long revision attributes, which could be exploited by attackers to cause a denial of service.
The fourth issue is due to a buffer overflow error in "elogd.c" when writing to the log file, which could be exploited by attackers to execute arbitrary commands or cause a denial of service.
The fifth flaw is due to a design error where the application displays different error messages for invalid passwords and invalid users, which could allow an attacker to probe for valid user names.
The sixth vulnerability is due to an infinite redirection error in "elogd.c" when handling the "fail" parameter, which could be exploited by attackers to cause a denial of service.
|
November 02, 2006 |
November 28, 2006 |
Six different vulnerabilities | prior to 2.6.3 | Critical | Upgrade to version 2.6.3 | Two vulnerabilities were identified in ELOG, which could be exploited by remote attackers to execute arbitrary commands or cause a denial of service.
The first issue is due to a format string error in the "write_logfile()" [elogd.c] function that does not properly handle a specially crafted username, which could be exploited by unauthenticated remote attackers to crash or compromise a vulnerable system.
The second vulnerability is due to an input validation error when processing specially crafted HTTP requests containing directory traversal sequences, which could be exploited by remote attackers to disclose the contents of arbitrary files present on a vulnerable system.
The third vulnerability is due to an error in the "elogd.c" file that does not properly handle overly long revision attributes, which could be exploited by attackers to cause a denial of service.
The fourth issue is due to a buffer overflow error in "elogd.c" when writing to the log file, which could be exploited by attackers to execute arbitrary commands or cause a denial of service.
The fifth flaw is due to a design error where the application displays different error messages for invalid passwords and invalid users, which could allow an attacker to probe for valid user names.
The sixth vulnerability is due to an infinite redirection error in "elogd.c" when handling the "fail" parameter, which could be exploited by attackers to cause a denial of service.
|
December 20, 2005 |
February 14, 2005 |
Overly large parameters can cause execution of arbitrary code (buffer overflow) | prior to 2.5.7 | High | Upgrade to version 2.5.7 | A vulnerability has been identified in ELOG, which could be exploited by remote attackers to cause a denial of service. This flaw is due to an input validation error in "elogd" that does not properly handle an overly large value passed to the "cmd" and "mode" parameters, which could be exploited by remote attackers to crash a vulnerable system.
|
November 10, 2006 |
November 28, 2006 |
ELOG can be crashed with a specially crafted URL | prior to 2.6.3 | Medium | Upgrade to version 2.6.3 | A vulnerability has been identified in ELOG, which could be exploited by attackers to cause a denial of service. This flaw is due to a NULL pointer dereference error when handling a specially crafted URL with a logbook set to "global", which could be exploited by malicious users to crash a vulnerable application, creating a denial of service condition.
|
January 24, 2008 |
January 30, 2008 |
Cross-site scripting vulnerability | prior to 2.7.2 | Low | Upgrade to version 2.7.2 | Requests using hand-crafted URLs can execute arbitrary script code. |
|