[asterisk-bugs] [Asterisk 0016810]: Dialplan language does not deal with & character safely

[Asterisk Bug Tracker]

The RELATED issue 0016808 has been RESOLVED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16810 
====================================================================== 
Reported By:                Nick_Lewis
Assigned To:                lmadsen
====================================================================== 
Project:                    Asterisk
Issue ID:                   16810
Category:                   Core/PBX
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
JIRA:                       SWP-900 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-02-11 08:06 CST
Last Modified:              2010-02-12 08:46 CST
====================================================================== 
Summary:                    Dialplan language does not deal with & character
safely
Description: 
The dialplan language uses the & character to represent arrays. For example
123&456&789 is an array of three elements 123, 456 and 789. However the
dialplan language does not prohibit (or escape) the use of a & character in
an array element. This means that the content of an element can cause the
execution of code when passed to a function (in this case the creation of a
new element) 
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
parent of           0016808 Create example documentation for usage ...
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-13 03:07 oej            Issue Monitored: oej                         
======================================================================