CVE-2004-2069

Description

sshd.c in OpenSSH 3.6.1p2 and 3.7.1p2 and possibly other versions, when using privilege separation, does not properly signal the non-privileged process when a session has been terminated after exceeding the LoginGraceTime setting, which leaves the connection open and allows remote attackers to cause a denial of service (connection consumption).

5.0

CVSS

Severity: Medium

CVSS 2.0 •

EPSS 4.85% Top 15%

Vendor Advisory securityfocus.com Vendor Advisory redhat.com

Affected: n/a n/a

References

Link	Tags
http://support.avaya.com/elmodocs2/security/ASA-2005-216.pdf
http://www.vmware.com/support/vi3/doc/esx-3069097-patch.html
http://www.vupen.com/english/advisories/2006/4502	vdb entry
http://marc.info/?l=openssh-unix-dev&m=107520317020444&w=2	mailing list
http://www.osvdb.org/16567	vdb entry
http://secunia.com/advisories/22875	third party advisory
http://secunia.com/advisories/23680	third party advisory
https://exchange.xforce.ibmcloud.com/vulnerabilities/20930	vdb entry
http://www.vmware.com/download/esx/esx-202-200610-patch.html
http://www.securityfocus.com/archive/1/451426/100/200/threaded	mailing list
http://www.securityfocus.com/archive/1/425397/100/0/threaded	vendor advisory
http://www.vmware.com/download/esx/esx-213-200610-patch.html
http://marc.info/?l=openssh-unix-dev&m=107529205602320&w=2	mailing list
http://support.avaya.com/elmodocs2/security/ASA-2005-223.pdf
http://secunia.com/advisories/17000	third party advisory
http://www.securityfocus.com/bid/14963	vdb entry
http://secunia.com/advisories/17252	third party advisory
http://secunia.com/advisories/17135	third party advisory
http://www.securityfocus.com/archive/1/451404/100/0/threaded	mailing list
https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11541	signature vdb entry
http://rhn.redhat.com/errata/RHSA-2005-550.html	vendor advisory
http://www.securityfocus.com/archive/1/451417/100/200/threaded	mailing list
http://www.vmware.com/support/vi3/doc/esx-9986131-patch.html

Frequently Asked Questions

What is the severity of CVE-2004-2069?: CVE-2004-2069 has been scored as a medium severity vulnerability.
How to fix CVE-2004-2069?: To fix CVE-2004-2069, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2004-2069 being actively exploited in the wild?: It is possible that CVE-2004-2069 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~5% probability that this vulnerability will be exploited by malicious actors in the next 30 days.