{"vuid":"VU#601312","idnumber":"601312","name":"Lotus Domino vulnerable to DoS via crafted HTTP header requests","keywords":["Lotus","Domino","header"],"overview":"The Lotus Domino Web Server contains a flaw that could be exploited to cause a denial of service.","clean_desc":"HTTP requests with uniquely crafted headers using \"Accept\", \"Accept-Charset\", \"Accept-Encoding\", \"Accept-Language\" or \"Content-Type\" are not freed properly. This means that submitting numerous requests for a document, such as root (/), with various accept fields (accept: a, accept: aa, accept: aaa, ...) will cause the server to run out of physical memory. The server will then display an error message similar to this one: \"HTTP Server: Could allocate 8036 bytes of memoryOut of memory in HTMemPoolAlloc (file htmpool.c, line 506).Program aborted.\" One of two things will then happen: 1) Processes that required working threads such as Task Manager will cease to function and the Lotus Server, while continuing to run, will no longer answer requests on TCP port 80. Also, any occupied memory will not be released. or 2) The Lotus Server process will crash, and will need to be restarted in order to regain functionality. The rest of the services, unrelated to the Lotus Server, on the host will continue to function normally.","impact":"The server will eventually run out of physical memory and a denial of service will result.","resolution":"Upgrade to Notes/Domino 5.0.7 or later. See http://www.notes.net/qmrdown.nsf/QMRWelcome.","workarounds":"An application layer filter may be able to detect and block unapproved requests.","sysaffected":"","thanks":"Our thanks to \nDefcom Labs\n, which published an advisory on this and other problems, available at \nhttp://www.securityfocus.com/frames/?content=/templates/advisory.html?id=3208.","author":"This document was written by Jason Rafail and is based on information obtained from a Defcom Labs Advisory.","public":["http://www.securityfocus.com/bid/2565","http://xforce.iss.net/static/6347.php","http://www.securityfocus.com/advisories/3208","http://www.notes.net/r5fixlist.nsf/a8f0ffda1fc76c8985256752006aba6c?OpenView&Start=3.111&Count=30&Expand=3.126#3.126"],"cveids":[""],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2001-04-13T23:56:55Z","publicdate":"2001-04-11T00:00:00Z","datefirstpublished":"2001-07-12T20:35:40Z","dateupdated":"2001-07-17T19:15:15Z","revision":19,"vrda_d1_directreport":"","vrda_d1_population":"","vrda_d1_impact":"","cam_widelyknown":"20","cam_exploitation":"0","cam_internetinfrastructure":"5","cam_population":"7","cam_impact":"8","cam_easeofexploitation":"19","cam_attackeraccessrequired":"20","cam_scorecurrent":"9.975","cam_scorecurrentwidelyknown":"9.975","cam_scorecurrentwidelyknownexploited":"17.955","ipprotocol":"","cvss_accessvector":"","cvss_accesscomplexity":"","cvss_authentication":null,"cvss_confidentialityimpact":"","cvss_integrityimpact":"","cvss_availabilityimpact":"","cvss_exploitablity":null,"cvss_remediationlevel":"","cvss_reportconfidence":"","cvss_collateraldamagepotential":"","cvss_targetdistribution":"","cvss_securityrequirementscr":"","cvss_securityrequirementsir":"","cvss_securityrequirementsar":"","cvss_basescore":"","cvss_basevector":"","cvss_temporalscore":"","cvss_environmentalscore":"","cvss_environmentalvector":"","metric":9.975,"vulnote":null}