Contents
This is an overview of changes in the CodeQL CLI and relevant CodeQL query and library packs. For additional updates on changes to the CodeQL code scanning experience, check out the code scanning section on the GitHub blog, relevant GitHub Changelog updates, changes in the CodeQL extension for Visual Studio Code, and the CodeQL Action changelog.
Security Coverage¶CodeQL 2.19.1 runs a total of 426 security queries when configured with the Default suite (covering 164 CWE). The Extended suite enables an additional 128 queries (covering 34 more CWE).
CodeQL CLI¶ New Features¶The command codeql generate query-help now supports Markdown help files. The Markdown help format is commonly used in custom CodeQL query packs. This new feature allows us to generate SARIF reporting descriptors for CodeQL queries that include Markdown help directly from a query Markdown help file.
Added a new command, codeql resolve packs. This command shows each step in the pack search process, including what packs were found in each step. With the --show-hidden-packs option, it can also show details on which packs were hidden by packs found earlier in the search sequence. codeql resolve packs is intended as a replacement for most uses of codeql resolve qlpacks, whose output is both less detailed and less accurate.
Fixed false positives in the cpp/wrong-number-format-arguments (“Too few arguments to formatting function”) query when the formatting function has been declared implicitly.
C#: The indexer and Add method on System.Web.UI.AttributeCollection is no longer considered an HTML sink.
Added taint summary model for org.springframework.core.io.InputStreamSource#getInputStream().
The experimental py/cors-misconfiguration-with-credentials query, which finds insecure CORS middleware configurations.
The precision of the go/incorrect-integer-conversion-query query was decreased from very-high to high, since there is at least one known class of false positives involving dynamic bounds checking.
C#: Add support for MaD directly on properties and indexers using attributes. Using Attribute.Getter or Attribute.Setter in the model ext field applies the model to the getter or setter for properties and indexers. Prior to this change Attribute models unintentionally worked for property setters (if the property is decorated with the matching attribute). That is, a model that uses the Attribute feature directly on a property for a property setter needs to be changed to Attribute.Setter.
C#: Remove all CIL tables and related QL library functionality.
DataFlow::Node instances are no longer created for library methods and fields that are not callable (either statically or dynamically) or otherwise referred to from source code. This may affect third-party queries that use these nodes to identify library methods or fields that are present in DLL files where those methods or fields are unreferenced. If this presents a problem, consider using Callable and other non-dataflow classes to identify such library entities.
C#: Add extractor support for attributes on indexers.
A method in the method set of an embedded field of a struct should not be promoted to the method set of the struct if the struct has a method with the same name. This was not being enforced, which meant that there were two methods with the same qualified name, and models were sometimes being applied when they shouldn’t have been. This has now been fixed.
The common sanitizer guard StringConstCompareBarrier has been renamed to ConstCompareBarrier and expanded to cover comparisons with other constant values such as None. This may result in fewer false positive results for several queries.
All AST classes in codeql.swift.elements are now final, which means that it is no longer possible to override predicates defined in those classes (it is, however, still possible to extend the classes).
The class ThreatModelFlowSource has been renamed to ActiveThreatModelSource to more clearly reflect it only contains the currently active threat model sources. ThreatModelFlowSource has been marked as deprecated.
The class ThreatModelFlowSource has been renamed to ActiveThreatModelSource to more clearly reflect it only contains the currently active threat model sources. ThreatModelFlowSource has been marked as deprecated.
The Field.getSourceDeclaration() predicate has been deprecated. The result was always the original field, so calls to it can simply be removed.
The Field.isSourceDeclaration() predicate has been deprecated. It always holds.
The RefType.nestedName() predicate has been deprecated, and RefType.getNestedName() added to replace it.
The class ThreatModelFlowSource has been renamed to ActiveThreatModelSource to more clearly reflect it only contains the currently active threat model sources. ThreatModelFlowSource has been marked as deprecated.
The Java extractor and QL libraries now support Java 23.
Kotlin versions up to 2.1.0x are now supported.
Added support for custom threat-models, which can be used in most of our taint-tracking queries, see our documentation for more details.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4