instal the new Universal Virus Sniffer 4.15

Customers who use older releases of CodeQL for security scanning in an automated CI system and cannot upgrade for compliance reasons can continue using that version. Other than upgrading, workarounds include not accepting CodeQL databases or queries from untrusted sources, or only processing such material on a machine without an Internet connection. The problem is fixed in release 2.16.3 of the CodeQL CLI. In particular, extracting XML files from a source tree into the CodeQL database does not make one vulnerable. Those using CodeQL for routine analysis of source trees with a preselected set of trusted queries are not affected. A single untrusted `.ql` or `.qll` file cannot be affected, but a zip archive or tarball containing QL sources may unpack auxiliary files that will trigger an attack when CodeQL sees them in the file system.

Security researchers and QL authors who receive databases or QL source files from untrusted sources may be impacted. This may result in a loss of privacy of exfiltration of secrets. If a vulnerable version of the CLI is used to process either a maliciously modified CodeQL database, or a specially prepared set of QL query sources, the CLI can be made to make an outgoing HTTP request to an URL that contains material read from a local file chosen by the attacker. Prior to version 2.16.3, an XML parser used by the CodeQL CLI to read various auxiliary files is vulnerable to an XML External Entity attack. The CodeQL CLI repo holds binaries for the CodeQL command line interface (CLI). SQL Injection vulnerability in CRMEB crmeb_java v.1.3.4 and before allows a remote attacker to obtain sensitive information via the latitude and longitude parameters in the api/front/store/list component.

Instal the new Universal Virus Sniffer 4.15