[asterisk-bugs] [Asterisk 0014362]: [patch] Putting a comma in an extension dialpattern causes eventual seg fault

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14362 
====================================================================== 
Reported By:                Nick_Lewis
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   14362
Category:                   Core/PBX
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           1.6.1-beta4 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-01-29 07:25 CST
Last Modified:              2009-01-30 08:02 CST
====================================================================== 
Summary:                    [patch] Putting a comma in an extension dialpattern
causes eventual seg fault
Description: 
If there is erroneously a comma in an extension dialpattern such as 

_9[1-3,5-9]. 

this leads some time later to a segmentation fault by various *s2=???
assignments in add_exten_to_pattern_tree() of pbx.c

There looks to be a string-unbounded while loop causing it 
====================================================================== 

---------------------------------------------------------------------- 
 (0099125) blitzrage (administrator) - 2009-01-30 08:02
 http://bugs.digium.com/view.php?id=14362#c99125 
---------------------------------------------------------------------- 
exten => _\[funny\,strange&weird\][\,\-;]\\etc\\,1,noop()

I would strong advocate *against* that format.

It is ugly, and makes writing further lines of dialplan extremely hard
(although I suppose now we have the 'same' priority... so it might not be
quite so bad).

But still, my first reaction to seeing that syntax was negative :) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-30 08:02 blitzrage      Note Added: 0099125                          
======================================================================