Missing issue in rules.xml about zap-sonar-plugin

[stevespringett]

Can you provide a pull request or an example XML file that uses this missing rule?

[jukkaharkki]

Just added this to rules.xml. Description take from that discussion over 30002

<rule>
    <key>30002</key>
    <name>Check for proper format string handling in back end c code</name>
    <description>
        <![CDATA[<h3>Solution :</h3>
    <p>Many of the back end interfaces use a secondary programming language, often compiled,
       to interface to a variety of system functions.  C and C++ are two of the more popular
       "traditional" languages that are used.  The Format String exploit occurs when the submitted
       data of an input string is evaluated as a command by the application. In this way,
       the attacker could execute code, read the stack, or cause a segmentation fault in the
       running application, causing new behaviors that could compromise the security or the
       stability of the system.</p>
    <h3>References:</h3>
    <ul>
    <li>No Reference.</li>
    </ul>]]>
    </description>
    <severity>MAJOR</severity>
    <status>READY</status>
    <tag>security</tag>
    <tag>zaproxy</tag>
</rule>

[stevespringett]

Thanks @jukkaharkki
Fix has been committed.