[PROTON-1380] Cyrus SASL accesses strings that have been freed

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: proton-0.16.0
• Fix Version/s: proton-c-0.17.0
• Component/s: proton-c
• Assignee: Andrew Stitcher
• Reporter: Ted Ross
• Created: 04/Jan/17 16:24
• Updated: 08/Feb/17 18:59
• Resolved: 04/Jan/17 19:52

Description

If a proton-c user calls pn_sasl_config_name or pn_sasl_config_path, the literal defaults are replaced with allocated duplicates of the supplied name or path. When the user's transport is eventually freed, these allocated strings are also freed (in pn_sasl_free).

Cyrus SASL retains a global pointer to this freed string and references it the next time a transport is created. Since the SASL initialization only occurs once per process, the strings are not refreshed and the SASL library continues to refer to the freed string.

There does not appear to be a workaround available for this issue.

Issue Links

• is depended upon by: DISPATCH-601 Valgrind errors in dispatch tests