libldap-ruby has memory corruption errors

Bug #273732 reported by aprotim on 2008-09-23
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libldap-ruby (Debian)
Fix Released
libldap-ruby (Ubuntu)

Bug Description

Libruby ldap creates LDAP::Mod objects by copying pointers, not strings, which means that when the original string is garbage collected, the Mod objects are corrupted.

Attached is a patch that is also being submitted upstream, but as similar bugs have been reported years ago with no response, not holding out a lot of hope on timely response.

aprotim (aprotim) wrote :
Artur Rona (ari-tczew) on 2009-09-19
affects: debian → libldap-ruby (Debian)
Changed in libldap-ruby (Debian):
importance: Unknown → Undecided
status: Confirmed → New
scm (scm) on 2011-02-17
tags: added: glucid lucid


Can you provide a test-case, a code snippet, which would demonstrate the bug? I understand it is memory corruption, and it depends on the behavior of the garbage collector and the activity on the system. But still, it would be useful to have something to reproduce the bug.

Dave Walker (davewalker) wrote :

I have uploaded a fix for this to a PPA based on the patch attached (thanks). Note, this package should only be used to prove a test case - so we can progress for an SRU.


Changed in libldap-ruby (Debian):
importance: Undecided → Unknown
status: New → Unknown
Changed in libldap-ruby (Debian):
status: Unknown → Confirmed
Changed in libldap-ruby (Debian):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.