Bug 559921 (CVE-2010-0305)
Summary: | CVE-2010-0305 ejabberd: Remote DoS via flood of client2server messages | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | Jan Lieskovsky <jlieskov> |
Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | unspecified | CC: | lemenkov |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://support.process-one.net/browse/EJAB-1173 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-08-22 15:01:28 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 559925 | ||
Bug Blocks: |
Description
Jan Lieskovsky
2010-01-29 10:52:50 UTC
This issue affects the latest versions of ejabberd package, as shipped with Fedora 11 (ejabberd-2.1.1-1.fc11) and 12 (ejabberd-2.1.1-1.fc12). This issue affects the latest version of ejabberd package, as shipped with EPEL-5 project (ejabberd-2.0.5-8.el5). Please fix. ejabberd-2.1.2-2.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/ejabberd-2.1.2-2.fc12 ejabberd-2.1.2-2.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/ejabberd-2.1.2-2.fc11 This is CVE-2010-0305. ejabberd-2.1.2-2.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. ejabberd-2.1.2-2.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report. *** Bug 559890 has been marked as a duplicate of this bug. *** *** Bug 559909 has been marked as a duplicate of this bug. *** |