Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CVE-2018-1089 389-ds-base: ns-slapd crash via large filter value in ldapsearch #2720

Closed
389-ds-bot opened this issue Sep 13, 2020 · 4 comments
Labels
closed: fixed Migration flag - Issue
Milestone

Comments

@389-ds-bot
Copy link

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/49661


Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1559819

It is possible to crash ns-slapd (and ipa-dnskeysyncd afterwards) with crafted ldapsearch query with very long filter value both as anonymous or authenticated user. The crash can be similarly triggered with a query via the FreeIPA API as an authenticated user.
@389-ds-bot 389-ds-bot added the closed: fixed Migration flag - Issue label Sep 13, 2020
@389-ds-bot 389-ds-bot added this to the 1.2.11 milestone Sep 13, 2020
@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2018-05-08 16:53:23

Metadata Update from @mreynolds389:

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2018-05-08 16:53:58

Metadata Update from @mreynolds389:

  • Issue assigned to mreynolds389

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2018-05-08 17:06:59

d77c7f0..9d8d096 master -> master

eb08d43..a589008 389-ds-base-1.3.8 -> 389-ds-base-1.3.8

8bdcfa4..056d75c 389-ds-base-1.3.7 -> 389-ds-base-1.3.7

99ba446..62ac4ec 389-ds-base-1.3.6 -> 389-ds-base-1.3.6

f4a76bb..2728983 389-ds-base-1.2.11 -> 389-ds-base-1.2.11

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2018-05-08 17:07:00

Metadata Update from @mreynolds389:

  • Custom field component adjusted to None
  • Custom field origin adjusted to None
  • Custom field reviewstatus adjusted to None
  • Custom field type adjusted to None
  • Custom field version adjusted to None
  • Issue close_status updated to: fixed
  • Issue set to the milestone: 1.2.11 (was: 0.0 NEEDS_TRIAGE)
  • Issue status updated to: Closed (was: Open)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: fixed Migration flag - Issue
Projects
None yet
Development

No branches or pull requests

1 participant