Bug 530719 (CVE-2009-3639)
Summary: | CVE-2009-3639 ProFTPD: Doesn't properly handle NULL character in subjectAltName | ||
---|---|---|---|
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: | matthias |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://bugs.proftpd.org/show_bug.cgi?id=3275 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-08-22 14:50:41 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: | 537899, 537900 | ||
Bug Blocks: |
Description
Jan Lieskovsky
2009-10-24 13:30:11 UTC
This issue affects the versions of the ProFTPD package, as shipped with Fedora releases of 10 and 11 (proftpd-1.3.2a-5.fc{10,11}), and as shipped within Extra Packages for Enterprise Linux 4 and 5 (EPEL-4, EPEL-5) projects (proftpd-1.3.2a-5.el{4,5}). Please fix. This issue does NOT affect the versions of the ProFTPD package, as scheduled to appear in Fedora release of 12 and 13 (proftpd-1.3.2b-1.fc12 and proftpd-1.3.2b-1.fc13) - these are already fixed. I'd say impact of this flaw should be pretty low. Reading the upstream bug, this problem occurs when ProFTPD's mod_tls is configured to check subjectAltName in _client's_ certificates against _client's_ IP/hostname (client IP address is resolved to hostname and that hostname is resolved back to IP, if you can get to the same IP (basic sanity check), hostname is compared to the subjectAltName in the certificate). I'm not aware of any other SSL server doing a check like this, as this is a bit strange feature. SSL server certificate checks are used to make sure you're talking to the right server making sure you can't get tricked by malicious / owned DNS. This check, however, relies on security of DNS... So as far as I can see, this can be used by client to bypass intended source host name restriction. Attacker needs to have a valid client certificate that is accepted by ProFTPD, with specially crafted sAN what would allow him to connect from other host than intended. So rather limited impact, and probably not very often used check / restriction. proftpd-1.3.2b-1.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/proftpd-1.3.2b-1.fc11 proftpd-1.3.2b-1.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/proftpd-1.3.2b-1.fc10 proftpd-1.3.2b-1.el5 has been submitted as an update for Fedora EPEL 5. http://admin.fedoraproject.org/updates/proftpd-1.3.2b-1.el5 proftpd-1.3.2b-1.el4 has been submitted as an update for Fedora EPEL 4. http://admin.fedoraproject.org/updates/proftpd-1.3.2b-1.el4 proftpd-1.3.2b-1.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report. proftpd-1.3.2b-1.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report. proftpd-1.3.2b-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report. proftpd-1.3.2b-1.el4 has been pushed to the Fedora EPEL 4 stable repository. If problems still persist, please make note of it in this bug report. |