Bug 999634 (CVE-2013-4283) - CVE-2013-4283 389-ds-base: ns-slapd crash due to bogus DN
Summary: CVE-2013-4283 389-ds-base: ns-slapd crash due to bogus DN
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2013-4283
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard: impact=important,public=20130828,repo...
Depends On: 1000631 1000632 1000633 1000634 1002215 1002216
Blocks: 1000630
TreeView+ depends on / blocked
 
Reported: 2013-08-21 18:16 UTC by Chris Hudson
Modified: 2019-06-08 19:41 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-24 15:58:41 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:1182 normal SHIPPED_LIVE Important: 389-ds-base security update 2013-08-28 20:03:16 UTC

Comment 6 Vincent Danen 2013-08-23 22:11:15 UTC
It was discovered that ns-slapd in 389 suffered from a flaw where a remote unauthenticated user able to send a MOD operation on a bogus DN to the 389 Directory Server and cause it to crash.

Comment 9 Vincent Danen 2013-08-23 22:25:26 UTC
This issue does not affect Red Hat Directory Server 8.

Comment 14 Vincent Danen 2013-08-28 15:55:56 UTC
Created 389-ds-base tracking bugs for this issue:

Affects: fedora-all [bug 1002215]
Affects: epel-5 [bug 1002216]

Comment 15 errata-xmlrpc 2013-08-28 16:04:59 UTC
This issue has been addressed in following products:

  Red Hat Enterprise Linux 6

Via RHSA-2013:1182 https://rhn.redhat.com/errata/RHSA-2013-1182.html

Comment 16 Fedora Update System 2013-08-30 22:56:12 UTC
389-ds-base-1.3.0.8-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 17 Fedora Update System 2013-08-30 23:02:53 UTC
389-ds-base-1.3.1.7-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.