Lotus Domino R5 Server DIIOP DoS Vulnerability
BID:2599
Info
Lotus Domino R5 Server DIIOP DoS Vulnerability
| Bugtraq ID: | 2599 |
| Class: | Input Validation Error |
| CVE: | |
| Remote: | Yes |
| Local: | No |
| Published: | Apr 11 2001 12:00AM |
| Updated: | Apr 11 2001 12:00AM |
| Credit: | Discovered and posted to Bugtraq by <[email protected]> on April 11, 2001. |
| Vulnerable: |
Lotus Domino 5.0.6 Lotus Domino 5.0.5 Lotus Domino 5.0.4 Lotus Domino 5.0.3 Lotus Domino 5.0.2 Lotus Domino 5.0.1 |
| Not Vulnerable: |
Lotus Domino 5.0.7 |
Discussion
Lotus Domino R5 Server DIIOP DoS Vulnerability
A denial of service condition can be exploited on a host running Lotus Domino R5 Server.
DIIOP by default listens on port 63148. Making continuous and unusually large connection requests to port 63148, will invoke a DIIOP session. Each such connection request will launch a new DIIOP session. Eventually this process will cause CPU utilization to spike to 100% on the target host.
A denial of service condition can be exploited on a host running Lotus Domino R5 Server.
DIIOP by default listens on port 63148. Making continuous and unusually large connection requests to port 63148, will invoke a DIIOP session. Each such connection request will launch a new DIIOP session. Eventually this process will cause CPU utilization to spike to 100% on the target host.
Exploit / POC
Lotus Domino R5 Server DIIOP DoS Vulnerability
Currently the SecurityFocus staff are not aware of any exploits for this issue. If you feel we are in error or are aware of more recent information, please mail us at: [email protected] <mailto:[email protected]>.
Currently the SecurityFocus staff are not aware of any exploits for this issue. If you feel we are in error or are aware of more recent information, please mail us at: [email protected] <mailto:[email protected]>.
Solution / Fix
Lotus Domino R5 Server DIIOP DoS Vulnerability
Solution:
Lotus has addressed this issue in version 5.0.7:
http://www.notes.net/qmrdown.nsf/QMRWelcome
Solution:
Lotus has addressed this issue in version 5.0.7:
http://www.notes.net/qmrdown.nsf/QMRWelcome