openldap-bugs August 2026

openldap-bugs@openldap.org

1 participants
239 discussions

[Issue 10522] New: Heap-buffer-overflow in mdb_cursor_last
by openldap-its＠openldap.org 07 Aug '26

07 Aug '26

https://bugs.openldap.org/show_bug.cgi?id=10522 Issue ID: 10522 Summary: Heap-buffer-overflow in mdb_cursor_last Product: LMDB Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: liblmdb Assignee: bugs(a)openldap.org Reporter: renault.cle(a)gmail.com Target Milestone: --- Created attachment 1155 --> https://bugs.openldap.org/attachment.cgi?id=1155&action=edit Reproducer for a heap-buffer-overflow Hello, I was fuzzing a bit LMDB on my personnal time and found memory issue. I attached the reproducer. It is only reproducible when compiled with ASan/UBSan (-fsanitize=address,undefined) on macOS and you can get a segfault on Linux (6.1.0-44-amd64, Debian 6.1.164-1). The issue appears in the mdb_cursor_last function line 8257 on commit 7bcb4d05da7cf1546133baf51178e5e1b53cdd53 from branch mdb.RE/1.0. Thank you for your help, Have a nice day PS: I cannot specify the right version in the version list. PS2: I get a 401 Authorization Required when I try to connect through GitHub from Arc Browser. -- You are receiving this mail because: You are on the CC list for the issue.

1 10

[Issue 7772] liblmdb sub-page growth when adding existing data
by openldap-its＠openldap.org 07 Aug '26

07 Aug '26

https://bugs.openldap.org/show_bug.cgi?id=7772 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|TEST |FIXED Status|RESOLVED |VERIFIED -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 8739] Better check for fsync on FreeBSD
by openldap-its＠openldap.org 07 Aug '26

07 Aug '26

https://bugs.openldap.org/show_bug.cgi?id=8739 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|TEST |FIXED Status|RESOLVED |VERIFIED -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 8590] LMDB: Suppress SIGPIPE in mdb_env_copythr on OS X
by openldap-its＠openldap.org 07 Aug '26

07 Aug '26

https://bugs.openldap.org/show_bug.cgi?id=8590 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED Resolution|TEST |FIXED -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 8335] MDB_MULTIPLE issues
by openldap-its＠openldap.org 07 Aug '26

07 Aug '26

https://bugs.openldap.org/show_bug.cgi?id=8335 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED Resolution|TEST |FIXED -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 9388] New: mdb_stat for DupSort DBI shows incorrect data
by openldap-its＠openldap.org 07 Aug '26

07 Aug '26

https://bugs.openldap.org/show_bug.cgi?id=9388 Issue ID: 9388 Summary: mdb_stat for DupSort DBI shows incorrect data Product: LMDB Version: 0.9.26 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: --- Component: liblmdb Assignee: bugs(a)openldap.org Reporter: AskAlexSharov(a)gmail.com Target Milestone: --- It doesn't include pages pages used for values. -- You are receiving this mail because: You are on the CC list for the issue.

1 4

[Issue 10557] slapo-chain installs an attacker-authored referral DN into a privileged operation on the trusted server
by openldap-its＠openldap.org 06 Aug '26

06 Aug '26

https://bugs.openldap.org/show_bug.cgi?id=10557 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED Group|OpenLDAP-devs | -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 10555] New: When configuring from static libcrypto.a and libssl.a, it errors: can't find openssl. To fix openssl static linking, just add -lpthread to the linker.
by openldap-its＠openldap.org 04 Aug '26

04 Aug '26

https://bugs.openldap.org/show_bug.cgi?id=10555 Issue ID: 10555 Summary: When configuring from static libcrypto.a and libssl.a, it errors: can't find openssl. To fix openssl static linking, just add -lpthread to the linker. Product: OpenLDAP Version: 2.6.13 Hardware: x86_64 OS: Linux Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: build Assignee: bugs(a)openldap.org Reporter: bee(a)mailsac.com Target Milestone: --- I am a newbie. Took 2 days to talk with ChatGPT and Gemini to analyze, configure, and config.log files. When configuring from static libcrypto.a and libssl.a, it errors: can't find openssl. To fix openssl static linking, just add -lpthread to the linker. ./configure \ --prefix=$HOME \ --enable-static \ --disable-shared \ --disable-debug \ --disable-dynamic \ --disable-syslog \ --disable-local \ --disable-slapd \ --enable-ipv6 \ --with-tls=openssl \ --without-cyrus-sasl \ --without-systemd \ --without-fetch \ --without-threads \ --without-yielding-select \ --without-mp \ --without-odbc \ --without-argon2 \ LIBS="-lpthread" # add -lpthread to fix openssl static linking -- You are receiving this mail because: You are on the CC list for the issue.

1 2

[Issue 10552] New: LMDB database getting corrupted
by openldap-its＠openldap.org 03 Aug '26

03 Aug '26

https://bugs.openldap.org/show_bug.cgi?id=10552 Issue ID: 10552 Summary: LMDB database getting corrupted Product: LMDB Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: liblmdb Assignee: bugs(a)openldap.org Reporter: donxenapo(a)gmail.com Target Milestone: --- We have deployed LMDB version 1.0.0 and we're getting corruption-type errors from some users. We don't have the exact number of affected users yet, but apparently deleting the database and recreating it seems to work around the issue. The error seems to happen either during a get or a put request, and once the database is corrupted, it will keep resulting in the same error for that user until the database is purged/recreated. Here are some examples of errors that we're getting: During Put: LMDB Put Failed Error: MDB_PROBLEM: Unexpected problem - txn should abort LMDB Put Failed Error: MDB_CORRUPTED: Located page was wrong type LMDB Put Failed Error: MDB_PAGE_NOTFOUND: Requested page not found During Get: LMDB Get Failed Error: MDB_PAGE_NOTFOUND: Requested page not found LMDB Get Failed Error: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid Sometimes it crashes during Put in memcpy, instead of returning an error. Call stack: memcpy(void) mdb_cursor_get mdb_txn_begin We're still in the process of collecting corrupted databases from our users, so we don't have any corruption examples yet. -- You are receiving this mail because: You are on the CC list for the issue.

1 14

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs August 2026