**Security finding fixed on line 51**

**Issue ID:** 1009
**CWE:** 89
**Issue Type:** Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
**Severity:** 4

**Description:**
<span>This database query contains a SQL injection flaw.  The call to java.sql.Statement.execute() constructs a dynamic SQL query using a variable derived from untrusted input.  An attacker could exploit this flaw to execute arbitrary SQL queries against the database. The first argument to execute() contains tainted data from the variable sqlQuery. The tainted data originated from an earlier call to AnnotationVirtualController.vc_annotation_entry.</span> <span>Avoid dynamically constructing SQL queries.  Instead, use parameterized prepared statements to prevent the database from interpreting the contents of bind variables as part of the query.  Always validate untrusted input to ensure that it conforms to the expected format, using centralized data validation routines when possible.</span> <span>References: <a href="https://cwe.mitre.org/data/definitions/89.html">CWE</a> <a href="https://owasp.org/www-community/attacks/SQL_Injection">OWASP</a></span>

This finding was addressed in the applied patch.

**Security finding fixed on line 40**

**Issue ID:** 1012
**CWE:** 89
**Issue Type:** Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
**Severity:** 4

**Description:**
<span>This database query contains a SQL injection flaw.  The call to java.sql.Statement.executeQuery() constructs a dynamic SQL query using a variable derived from untrusted input.  An attacker could exploit this flaw to execute arbitrary SQL queries against the database. The first argument to executeQuery() contains tainted data from the variable sqlQuery. The tainted data originated from an earlier call to AnnotationVirtualController.vc_annotation_entry.</span> <span>Avoid dynamically constructing SQL queries.  Instead, use parameterized prepared statements to prevent the database from interpreting the contents of bind variables as part of the query.  Always validate untrusted input to ensure that it conforms to the expected format, using centralized data validation routines when possible.</span> <span>References: <a href="https://cwe.mitre.org/data/definitions/89.html">CWE</a> <a href="https://owasp.org/www-community/attacks/SQL_Injection">OWASP</a></span>

This finding was addressed in the applied patch.

**Security finding fixed on line 47**

**Issue ID:** 1007
**CWE:** 89
**Issue Type:** Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
**Severity:** 4

**Description:**
<span>This database query contains a SQL injection flaw.  The call to java.sql.Statement.execute() constructs a dynamic SQL query using a variable derived from untrusted input.  An attacker could exploit this flaw to execute arbitrary SQL queries against the database. The first argument to execute() contains tainted data from the variable sqlQuery. The tainted data originated from earlier calls to AnnotationVirtualController.vc_annotation_entry, and java.sql.Statement.executeQuery.</span> <span>Avoid dynamically constructing SQL queries.  Instead, use parameterized prepared statements to prevent the database from interpreting the contents of bind variables as part of the query.  Always validate untrusted input to ensure that it conforms to the expected format, using centralized data validation routines when possible.</span> <span>References: <a href="https://cwe.mitre.org/data/definitions/89.html">CWE</a> <a href="https://owasp.org/www-community/attacks/SQL_Injection">OWASP</a></span>

This finding was addressed in the applied patch.

**Security finding fixed on line 47**

**Issue ID:** 1005
**CWE:** 89
**Issue Type:** Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
**Severity:** 4

**Description:**
<span>This database query contains a SQL injection flaw.  The call to java.sql.Statement.execute() constructs a dynamic SQL query using a variable derived from untrusted input.  An attacker could exploit this flaw to execute arbitrary SQL queries against the database. The first argument to execute() contains tainted data from the variable sqlQuery. The tainted data originated from earlier calls to AnnotationVirtualController.vc_annotation_entry, and java.sql.Statement.executeQuery.</span> <span>Avoid dynamically constructing SQL queries.  Instead, use parameterized prepared statements to prevent the database from interpreting the contents of bind variables as part of the query.  Always validate untrusted input to ensure that it conforms to the expected format, using centralized data validation routines when possible.</span> <span>References: <a href="https://cwe.mitre.org/data/definitions/89.html">CWE</a> <a href="https://owasp.org/www-community/attacks/SQL_Injection">OWASP</a></span>

This finding was addressed in the applied patch.

**Security finding fixed on line 40**

**Issue ID:** 1010
**CWE:** 89
**Issue Type:** Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
**Severity:** 4

**Description:**
<span>This database query contains a SQL injection flaw.  The call to java.sql.Statement.executeQuery() constructs a dynamic SQL query using a variable derived from untrusted input.  An attacker could exploit this flaw to execute arbitrary SQL queries against the database. The first argument to executeQuery() contains tainted data from the variable sqlQuery. The tainted data originated from an earlier call to AnnotationVirtualController.vc_annotation_entry.</span> <span>Avoid dynamically constructing SQL queries.  Instead, use parameterized prepared statements to prevent the database from interpreting the contents of bind variables as part of the query.  Always validate untrusted input to ensure that it conforms to the expected format, using centralized data validation routines when possible.</span> <span>References: <a href="https://cwe.mitre.org/data/definitions/89.html">CWE</a> <a href="https://owasp.org/www-community/attacks/SQL_Injection">OWASP</a></span>

This finding was addressed in the applied patch.

**Security finding fixed on line 167**

**Issue ID:** 1013
**CWE:** 89
**Issue Type:** Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
**Severity:** 4

**Description:**
<span>This database query contains a SQL injection flaw.  The call to java.sql.Statement.executeQuery() constructs a dynamic SQL query using a variable derived from untrusted input.  An attacker could exploit this flaw to execute arbitrary SQL queries against the database. The first argument to executeQuery() contains tainted data from the variable sqlQuery. The tainted data originated from an earlier call to AnnotationVirtualController.vc_annotation_entry.</span> <span>Avoid dynamically constructing SQL queries.  Instead, use parameterized prepared statements to prevent the database from interpreting the contents of bind variables as part of the query.  Always validate untrusted input to ensure that it conforms to the expected format, using centralized data validation routines when possible.</span> <span>References: <a href="https://cwe.mitre.org/data/definitions/89.html">CWE</a> <a href="https://owasp.org/www-community/attacks/SQL_Injection">OWASP</a></span>

This finding was addressed in the applied patch.

**Security finding fixed on line 248**

**Issue ID:** 1015
**CWE:** 89
**Issue Type:** Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
**Severity:** 4

**Description:**
<span>This database query contains a SQL injection flaw.  The call to java.sql.Statement.executeQuery() constructs a dynamic SQL query using a variable derived from untrusted input.  An attacker could exploit this flaw to execute arbitrary SQL queries against the database. The first argument to executeQuery() contains tainted data from the variable sql. The tainted data originated from an earlier call to AnnotationVirtualController.vc_annotation_entry.</span> <span>Avoid dynamically constructing SQL queries.  Instead, use parameterized prepared statements to prevent the database from interpreting the contents of bind variables as part of the query.  Always validate untrusted input to ensure that it conforms to the expected format, using centralized data validation routines when possible.</span> <span>References: <a href="https://cwe.mitre.org/data/definitions/89.html">CWE</a> <a href="https://owasp.org/www-community/attacks/SQL_Injection">OWASP</a></span>

This finding was addressed in the applied patch.

**Security finding fixed on line 310**

**Issue ID:** 1014
**CWE:** 89
**Issue Type:** Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
**Severity:** 4

**Description:**
<span>This database query contains a SQL injection flaw.  The call to java.sql.Statement.executeQuery() constructs a dynamic SQL query using a variable derived from untrusted input.  An attacker could exploit this flaw to execute arbitrary SQL queries against the database. The first argument to executeQuery() contains tainted data from the variable sql. The tainted data originated from an earlier call to AnnotationVirtualController.vc_annotation_entry.</span> <span>Avoid dynamically constructing SQL queries.  Instead, use parameterized prepared statements to prevent the database from interpreting the contents of bind variables as part of the query.  Always validate untrusted input to ensure that it conforms to the expected format, using centralized data validation routines when possible.</span> <span>References: <a href="https://cwe.mitre.org/data/definitions/89.html">CWE</a> <a href="https://owasp.org/www-community/attacks/SQL_Injection">OWASP</a></span>

This finding was addressed in the applied patch.

**Security finding fixed on line 483**

**Issue ID:** 1016
**CWE:** 89
**Issue Type:** Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
**Severity:** 4

**Description:**
<span>This database query contains a SQL injection flaw.  The call to java.sql.Statement.executeQuery() constructs a dynamic SQL query using a variable derived from untrusted input.  An attacker could exploit this flaw to execute arbitrary SQL queries against the database. The first argument to executeQuery() contains tainted data from the variable sqlMyEvents. The tainted data originated from earlier calls to AnnotationVirtualController.vc_annotation_entry, and java.sql.Statement.executeQuery.</span> <span>Avoid dynamically constructing SQL queries.  Instead, use parameterized prepared statements to prevent the database from interpreting the contents of bind variables as part of the query.  Always validate untrusted input to ensure that it conforms to the expected format, using centralized data validation routines when possible.</span> <span>References: <a href="https://cwe.mitre.org/data/definitions/89.html">CWE</a> <a href="https://owasp.org/www-community/attacks/SQL_Injection">OWASP</a></span>

This finding was addressed in the applied patch.

**Security finding fixed on line 494**

**Issue ID:** 1025
**CWE:** 89
**Issue Type:** Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
**Severity:** 4

**Description:**
<span>This database query contains a SQL injection flaw.  The call to java.sql.PreparedStatement.executeQuery() constructs a dynamic SQL query using a variable derived from untrusted input.  An attacker could exploit this flaw to execute arbitrary SQL queries against the database. executeQuery() was called on the myInfo object, which contains tainted data. The tainted data originated from earlier calls to AnnotationVirtualController.vc_annotation_entry, and java.sql.Statement.executeQuery.</span> <span>Avoid dynamically constructing SQL queries.  Instead, use parameterized prepared statements to prevent the database from interpreting the contents of bind variables as part of the query.  Always validate untrusted input to ensure that it conforms to the expected format, using centralized data validation routines when possible.</span> <span>References: <a href="https://cwe.mitre.org/data/definitions/89.html">CWE</a> <a href="https://owasp.org/www-community/attacks/SQL_Injection">OWASP</a></span>

This finding was addressed in the applied patch.

**Security finding fixed on line 495**

**Issue ID:** 1025
**CWE:** 89
**Issue Type:** Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
**Severity:** 4

**Description:**
<span>This database query contains a SQL injection flaw.  The call to java.sql.PreparedStatement.executeQuery() constructs a dynamic SQL query using a variable derived from untrusted input.  An attacker could exploit this flaw to execute arbitrary SQL queries against the database. executeQuery() was called on the myInfo object, which contains tainted data. The tainted data originated from earlier calls to AnnotationVirtualController.vc_annotation_entry, and java.sql.Statement.executeQuery.</span> <span>Avoid dynamically constructing SQL queries.  Instead, use parameterized prepared statements to prevent the database from interpreting the contents of bind variables as part of the query.  Always validate untrusted input to ensure that it conforms to the expected format, using centralized data validation routines when possible.</span> <span>References: <a href="https://cwe.mitre.org/data/definitions/89.html">CWE</a> <a href="https://owasp.org/www-community/attacks/SQL_Injection">OWASP</a></span>

This finding was addressed in the applied patch.

**Security finding fixed on line 40**

**Issue ID:** 1011
**CWE:** 89
**Issue Type:** Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
**Severity:** 4

**Description:**
<span>This database query contains a SQL injection flaw.  The call to java.sql.Statement.executeQuery() constructs a dynamic SQL query using a variable derived from untrusted input.  An attacker could exploit this flaw to execute arbitrary SQL queries against the database. The first argument to executeQuery() contains tainted data from the variable sqlQuery. The tainted data originated from an earlier call to AnnotationVirtualController.vc_annotation_entry.</span> <span>Avoid dynamically constructing SQL queries.  Instead, use parameterized prepared statements to prevent the database from interpreting the contents of bind variables as part of the query.  Always validate untrusted input to ensure that it conforms to the expected format, using centralized data validation routines when possible.</span> <span>References: <a href="https://cwe.mitre.org/data/definitions/89.html">CWE</a> <a href="https://owasp.org/www-community/attacks/SQL_Injection">OWASP</a></span>

This finding was addressed in the applied patch.

**Security finding fixed on line 47**

**Issue ID:** 1006
**CWE:** 89
**Issue Type:** Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
**Severity:** 4

**Description:**
<span>This database query contains a SQL injection flaw.  The call to java.sql.Statement.execute() constructs a dynamic SQL query using a variable derived from untrusted input.  An attacker could exploit this flaw to execute arbitrary SQL queries against the database. The first argument to execute() contains tainted data from the variable sqlQuery. The tainted data originated from earlier calls to AnnotationVirtualController.vc_annotation_entry, and java.sql.Statement.executeQuery.</span> <span>Avoid dynamically constructing SQL queries.  Instead, use parameterized prepared statements to prevent the database from interpreting the contents of bind variables as part of the query.  Always validate untrusted input to ensure that it conforms to the expected format, using centralized data validation routines when possible.</span> <span>References: <a href="https://cwe.mitre.org/data/definitions/89.html">CWE</a> <a href="https://owasp.org/www-community/attacks/SQL_Injection">OWASP</a></span>

This finding was addressed in the applied patch.