389-ds-base

#49173 Heap use after free in vattr
Closed: wontfix Opened by firstyear.

Closed: wontfix
Reopen Issue

Issue Description

I introduced an issue in vattar:

{root@ldapkdc 19:04} /opt/dirsrv/var/run/dirsrv I0> python /home/william/development/389ds/asan_symbolize_el7.py < ns-slapd-master_2.asan.12667
=================================================================
==12667== ERROR: AddressSanitizer: heap-use-after-free on address 0x600400d4a590 at pc 0x7f56a76c6c0d bp 0x7f565a29fb30 sp 0x7f565a29fb20
WRITE of size 8 at 0x600400d4a590 thread T42
==12667== AddressSanitizer CHECK failed: ../../../../libsanitizer/sanitizer_common/sanitizer_symbolizer_linux.cc:147 "((module_name_len)) != (((uptr)-1))" (0xffffffffffffffff, 0xffffffffffffffff)
    #0 0x7f56a8063dca in _ZdaPvRKSt9nothrow_t ??:?
    #1 0x7f56a806b033 in _ZN11__sanitizer11CheckFailedEPKciS1_yy ??:?
    #2 0x7f56a806fc4f in _ZN11__sanitizer10StackTrace15UncompressStackEPS0_Pjm ??:?
    #3 0x7f56a48fea5b in __dl_iterate_phdr :?
    #4 0x7f56a806ff89 in _ZN11__sanitizer10StackTrace15UncompressStackEPS0_Pjm ??:?
    #5 0x7f56a806f37d in _ZN11__sanitizer10StackTrace15UncompressStackEPS0_Pjm ??:?
    #6 0x7f56a806e8c6 in __sanitizer_report_error_summary ??:?
    #7 0x7f56a8069e06 in __asan_report_error ??:?
    #8 0x7f56a8064405 in __asan_report_store8 ??:?
    #9 0x7f56a76c6c0c in slapi_vattr_values_get_sp /home/william/development/389ds/ds/ldap/servers/slapd/vattr.c:757:0
    #10 0x7f56a76c1c3a in slapi_vattr_values_get /home/william/development/389ds/ds/ldap/servers/slapd/vattr.c:132:0
    #11 0x7f56a7595b11 in slapi_check_account_lock /home/william/development/389ds/ds/ldap/servers/slapd/pw.c:2288:0
    #12 0x420624 in do_bind /home/william/development/389ds/ds/ldap/servers/slapd/bind.c:725:0
    #13 0x43999e in connection_dispatch_operation /home/william/development/389ds/ds/ldap/servers/slapd/connection.c:608:0
    #14 0x444cd4 in connection_threadmain /home/william/development/389ds/ds/ldap/servers/slapd/connection.c:1772:0
    #15 0x7f56a54349ba in PR_Select ??:?
    #16 0x7f56a806aa97 in __asan_describe_address ??:?
    #17 0x7f56a51f7dc4 in start_thread pthread_create.c:?
    #18 0x7f56a48c473c in __clone ??:?

Generally affects replication only.

Metadata Update from @firstyear:
- Custom field reviewstatus adjusted to new
- Custom field type adjusted to defect
- Issue assigned to firstyear
- Issue priority set to: 2
- Issue tagged with: Hot

Fixed this in Issue 49169, closing as duplicate

Metadata Update from @mreynolds:
- Issue close_status updated to: duplicate
- Issue status updated to: Closed (was: Open)

Indeed, the test that was failing now passes.

We should be sure to run a full suite of tests with asan to flag anything else just in case.

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/2232

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: duplicate)
Metadata

Hot

None
None
Low
new
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.