openldap-bugs

openldap-bugs@openldap.org

1 participants
20967 discussions

Re: (ITS#8842) NULL pointer derefence
by ondra＠mistotebe.net 21 Jun '18

21 Jun '18

On Tue, May 01, 2018 at 08:14:50PM +0000, openldap(a)katzen.cc wrote: > 2 small issues: > I'm keeping it brief, let me know if you need more information. > > A malicious LDAP server or mitm attacker can craft a response that causes the > ldap client to crash. Nothing critical, just a simoke DoS. > [...] > The problem here is that retoid can be NULL after ldap_parse_intermediate() is > called. > > Another NULL pointer dereference caused by a bad response: > [...] > The PoC leads to memcpy being called with a NULL pointer as second argument > (ava->la_value.bv_val) in dn2domain() (libraries/libldap/getdn.c): > > AC_MEMCPY( str, ava->la_value.bv_val, ava->la_value.bv_len + 1); Both are fixed in this branch: https://github.com/mistotebe/openldap/tree/its8842 -- Ondřej Kuzník Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP

1 0

Re: (ITS#8866) RFE: slapo-constraint to return filter used in diagnostic message
by michael＠stroeder.com 20 Jun '18

20 Jun '18

On 06/20/2018 01:41 PM, Michael Ströder wrote: > Ouch! This was not yet complete. I'll come up with a new revision soon. Please review this patch: https://www.stroeder.com/temp/0001-ITS-8866-slapo-unique-to-return-filter-u… Disclaimer: I'm not a C programmer. Thanks for your patience. Ciao, Michael.

1 0

Re: (ITS#8866) RFE: slapo-constraint to return filter used in diagnostic message
by michael＠stroeder.com 20 Jun '18

20 Jun '18

On 06/20/2018 01:26 PM, michael(a)stroeder.com wrote: > Find the patch against master here: > https://www.stroeder.com/temp/0001-ITS-8866-slapo-unique-to-return-filter-u… Ouch! This was not yet complete. I'll come up with a new revision soon. Ciao, Michael.

1 0

Re: (ITS#8866) RFE: slapo-constraint to return filter used in diagnostic message
by michael＠stroeder.com 20 Jun '18

20 Jun '18

Rationale: This patch is meant to enhance user experience in case a client software is used to maintain data directly via LDAP. This is a real-world issue. Find the patch against master here: https://www.stroeder.com/temp/0001-ITS-8866-slapo-unique-to-return-filter-u… Also cleanly applies to RE24 and therefore could be easily added to upcoming release 2.4.47. ;-)

1 0

(ITS#8866) RFE: slapo-constraint to return filter used in diagnostic message
by michael＠stroeder.com 20 Jun '18

20 Jun '18

Full_Name: Version: OS: URL: Submission from: (NULL) (213.240.182.62) See motivation and disclosure considerations in list archive: https://www.openldap.org/lists/openldap-devel/201711/msg00003.html Patch will follow.

1 0

Re: (ITS#8844) LMDB mdb_env_close is unsafe in forked child
by h.b.furuseth＠usit.uio.no 14 Jun '18

14 Jun '18

On 14/06/2018 21:04, Howard Chu wrote: > Hallvard Breien Furuseth wrote: >> On 14/06/2018 20:34, Howard Chu wrote: >>> If there are any table entries under that PID there's no problem >>> removing them. >> >> The problem is that it's arbitrary. Something is exiting without >> clearing its pid slots, and 0.001% of the time this code will catch it. > > Sure. But I don't think it's worthwhile to make a special case here to > skip this step. To my eyes the getpid() is a special case already, to someone trying to understand the code. Though adding a comment could fix that. See below. >> Better to skip this cleanup, or to always do it - but "always" belongs >> in env_open(). If a new env is seeing its pid in use, then it can >> safely clean it out. Last we talked about that, I liked it and you >> did not:-) > > And I don't see any particular reason to add this step. right >>(...) >> Parent, pid P: >> open env A. >> >> Child, pid Q: >> - open and start using env B with the same path. >> - close env A, while B is still open. >> With the new code, this clears pid Q - i.e. B's pids. >> But lmdb.h already lists that as a "don't do that", >> because it also removes B's lock on the lockfile. >> > Yeah, this is still a "don't do that" though, regardless of this > particular ITS. Right. So in summary, there are two cases when getpid() can be there to clean out, and in neither case does it make sense to clean it out. Other than the sense of avoiding one "if () { init two vars; }". I like that better than a comment about not bothering to, but a comment is OK too.

1 0

Re: (ITS#8844) LMDB mdb_env_close is unsafe in forked child
by hyc＠symas.com 14 Jun '18

14 Jun '18

Hallvard Breien Furuseth wrote: > On 14/06/2018 20:34, Howard Chu wrote: >> Hallvard Breien Furuseth wrote: >>> Wait, what? The child didn't write any pids to the table. If >>> there are pids for it to clear, something is wrong. That can be: >> >> No, there most likely aren't PIDs for it to clear. But most importantly, it >> must not clear using env->me_pid since that is still the parent's PID. >> >>> - The pid is from an older run, and the system reused the pid. If we >>> code for this, it should be to clear such pids during mdb_env_open. >>> It gets very arbitrary to clear them when the user does env_close() >>> in the child and the child happens to have the that reused pid. >> >> No. If the system reused the PID then that means the previous owner of that >> PID is dead already anyway. > > Right... > >> If there are any table entries under that PID there's no problem removing them. > > The problem is that it's arbitrary. Something is exiting without > clearing its pid slots, and 0.001% of the time this code will catch it. Sure. But I don't think it's worthwhile to make a special case here to skip this step. > Better to skip this cleanup, or to always do it - but "always" belongs > in env_open(). If a new env is seeing its pid in use, then it can safely > clean it out. Last we talked about that, I liked it and you > did not:-) And I don't see any particular reason to add this step. >>> - The child opened a new MDB_env with the same path, and closes the >>> parent's env afterwards. Don't Do That, users. But what to do in >>> this situation, if we are to have code for it, is to do nothing with >>> the lockfile. Not close it either, since closing it will lose the >>> lock for the env which was opened in the child. >> >> That's a completely different case. This ITS is specifically about a process >> with an open environment that subsequently forks. > > No, I mean: > > Parent, pid P: > open env A. > > Child, pid Q: > - open and start using env B with the same path. > - close env A, while B is still open. > With the new code, this clears pid Q - i.e. B's pids. > But lmdb.h already lists that as a "don't do that", > because it also removes B's lock on the lockfile. > Yeah, this is still a "don't do that" though, regardless of this particular ITS. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#8844) LMDB mdb_env_close is unsafe in forked child
by h.b.furuseth＠usit.uio.no 14 Jun '18

14 Jun '18

On 14/06/2018 20:34, Howard Chu wrote: > Hallvard Breien Furuseth wrote: >> Wait, what? The child didn't write any pids to the table. If >> there are pids for it to clear, something is wrong. That can be: > > No, there most likely aren't PIDs for it to clear. But most importantly, > it must not clear using env->me_pid since that is still the parent's PID. > >> - The pid is from an older run, and the system reused the pid. If we >> code for this, it should be to clear such pids during mdb_env_open. >> It gets very arbitrary to clear them when the user does env_close() >> in the child and the child happens to have the that reused pid. > > No. If the system reused the PID then that means the previous owner of > that PID is dead already anyway. Right... > If there are any table entries under > that PID there's no problem removing them. The problem is that it's arbitrary. Something is exiting without clearing its pid slots, and 0.001% of the time this code will catch it. Better to skip this cleanup, or to always do it - but "always" belongs in env_open(). If a new env is seeing its pid in use, then it can safely clean it out. Last we talked about that, I liked it and you did not:-) >> - The child opened a new MDB_env with the same path, and closes the >> parent's env afterwards. Don't Do That, users. But what to do in >> this situation, if we are to have code for it, is to do nothing with >> the lockfile. Not close it either, since closing it will lose the >> lock for the env which was opened in the child. > > That's a completely different case. This ITS is specifically about a > process with an open environment that subsequently forks. No, I mean: Parent, pid P: open env A. Child, pid Q: - open and start using env B with the same path. - close env A, while B is still open. With the new code, this clears pid Q - i.e. B's pids. But lmdb.h already lists that as a "don't do that", because it also removes B's lock on the lockfile.

1 0

Re: (ITS#8844) LMDB mdb_env_close is unsafe in forked child
by hyc＠symas.com 14 Jun '18

14 Jun '18

Hallvard Breien Furuseth wrote: > On 02/05/2018 18:05, hyc(a)openldap.org wrote: >> Following on from ITS#8505. >> mdb_env_close0() uses env->me_pid when clearing the readers table. If the env >> was open in a process that forked, and the child process calls mdb_env_close(), >> it will be clearing the wrong PID. Change this to use getpid() instead. > > Wait, what? The child didn't write any pids to the table. If > there are pids for it to clear, something is wrong. That can be: No, there most likely aren't PIDs for it to clear. But most importantly, it must not clear using env->me_pid since that is still the parent's PID. > - The pid is from an older run, and the system reused the pid. If we > code for this, it should be to clear such pids during mdb_env_open. > It gets very arbitrary to clear them when the user does env_close() > in the child and the child happens to have the that reused pid. No. If the system reused the PID then that means the previous owner of that PID is dead already anyway. If there are any table entries under that PID there's no problem removing them. > - The child opened a new MDB_env with the same path, and closes the > parent's env afterwards. Don't Do That, users. But what to do in > this situation, if we are to have code for it, is to do nothing with > the lockfile. Not close it either, since closing it will lose the > lock for the env which was opened in the child. That's a completely different case. This ITS is specifically about a process with an open environment that subsequently forks. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

(ITS#8865) Publish admin guide in epub format
by dpa-bugs＠aegee.org 11 Jun '18

11 Jun '18

Full_Name: Dilian Palauzov Version: OS: URL: Submission from: (NULL) (87.118.146.153) Please offer the admin guide for downloading also in epub format. The guide is written in sdf, this could be converted to POD and then to EPUB. SDF offers also output in SGML, this can probably be converted to EPUB, too.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs