Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1382386

Summary:	Directory Server accepts a wrong userdn macro ACI
Product:	Red Hat Enterprise Linux 6	Reporter:	Simon Pichugin <spichugi>
Component:	389-ds-base	Assignee:	Noriko Hosoi <nhosoi>
Status:	CLOSED ERRATA	QA Contact:	Viktor Ashirov <vashirov>
Severity:	unspecified	Docs Contact:	Marc Muehlfeld <mmuehlfe>
Priority:	unspecified
Version:	6.8	CC:	nhosoi, nkinder, rmeggins
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	389-ds-base-1.2.11.15-84.el6	Doc Type:	Bug Fix
Doc Text:	Directory Server now validates macros in ACIs Previously, the Red Hat Directory Server did not validate macros in an access control instruction (ACI). As a result, users were able to set incorrect macros in an ACI. This update improves the code underlying validation, and Directory Server rejects invalid macros and logs an error.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-21 10:23:24 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Simon Pichugin 2016-10-06 14:22:17 UTC

Description of problem:
It is possible to add ACI with a wrong userdn macro in it.


Version-Release number of selected component (if applicable):
389-ds-base-1.2.11.15-74.el6.x86_64


How reproducible:
Always


Steps to Reproduce:
1. Install an instance with 'dc=example,dc=com' suffix
2. Add the setup like this:
$ ldapmodify -h localhost -p 389 -D "cn=Directory manager" -w Secret123
dn: o=MACRO.com, dc=example,dc=com
changetype: add
objectClass: top
objectClass: organization
o: MACRO.com
description: ou=Groups
 
adding new entry "o=MACRO.com, dc=example,dc=com"
 
dn: ou=Groups, o=MACRO.com, dc=example,dc=com
changetype: add
objectClass: top
objectClass: organizationalUnit
ou: Groups
 
adding new entry "ou=Groups, o=MACRO.com, dc=example,dc=com"
 
dn: cn=Macro, ou=Groups, o=MACRO.com, dc=example,dc=com
changetype: add
objectClass: top
objectClass: person
cn: Macro
sn: Macro
userPassword: Macro
 
adding new entry "cn=Macro, ou=Groups, o=MACRO.com, dc=example,dc=com"

3. Try to add ACI with a wrong userdn macro in it:
$ ldapmodify -h localhost -p 389 -D "cn=Directory manager" -w Secret123
dn: o=MACRO.com, dc=example,dc=com
changetype: modify
add: aci
aci: (target="ldap:///o=MACRO.com, dc=example,dc=com")(version 3.0; acl "Wrong_ACI_25"; allow (all) userdn="ldap:///cn=Macro, ($attr..description), o=MACRO.com, dc=example,dc=com";)


Actual results:
No error is occured.
modifying entry "o=MACRO.com, dc=example,dc=com"


Expected results:
Invalid syntax error.


Additional info:
It will pass the following macros, but it shouldn't:
- ($attr..description)
- ($attribute.description)
- ($att.$attr.description)
- ($attr#description)

Comment 7 Simon Pichugin 2016-12-01 06:06:44 UTC

Build tested:
389-ds-base-1.2.11.15-85.el6.x86_64

Verification steps:
1. Install an instance with 'dc=example,dc=com' suffix
2. Add the setup like this:
$ ldapmodify -h localhost -p 389 -D "cn=Directory manager" -w Secret123
dn: o=MACRO.com, dc=example,dc=com
changetype: add
objectClass: top
objectClass: organization
o: MACRO.com
description: ou=Groups
 
adding new entry "o=MACRO.com, dc=example,dc=com"
 
dn: ou=Groups, o=MACRO.com, dc=example,dc=com
changetype: add
objectClass: top
objectClass: organizationalUnit
ou: Groups
 
adding new entry "ou=Groups, o=MACRO.com, dc=example,dc=com"
 
dn: cn=Macro, ou=Groups, o=MACRO.com, dc=example,dc=com
changetype: add
objectClass: top
objectClass: person
cn: Macro
sn: Macro
userPassword: Macro
 
adding new entry "cn=Macro, ou=Groups, o=MACRO.com, dc=example,dc=com"

3. Try to add ACI with a wrong userdn macro in it.
Check the following macros, they all should be "Invalid syntax":
- ($attr..description)
- ($attribute.description)
- ($att.$attr.description)
- ($attr#description)

$ ldapmodify -h localhost -p 389 -D "cn=Directory manager" -w Secret123
dn: o=MACRO.com, dc=example,dc=com
changetype: modify
add: aci
aci: (target="ldap:///o=MACRO.com, dc=example,dc=com")(version 3.0; acl "Wrong_ACI_25"; allow (all) userdn="ldap:///cn=Macro, ($attr..description), o=MACRO.com, dc=example,dc=com";)

modifying entry "o=MACRO.com, dc=example,dc=com"
ldap_modify: Invalid syntax (21)
        additional info: ACL Syntax Error(-5):(target=\22ldap:///o=MACRO.com, dc=example,dc=com\22)(version 3.0; acl \22Wrong_ACI_25\22; allow (all) userdn=\22ldap:///cn=Macro, ($attr..description), o=MACRO.com, dc=example,dc=com\22;)

Wrong syntax macros fails. Marking as VERIFIED.

Comment 11 errata-xmlrpc 2017-03-21 10:23:24 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2017-0667.html