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.14.0 runs a total of 390 security queries when configured with the Default suite (covering 155 CWE). The Extended suite enables an additional 127 queries (covering 33 more CWE). 2 security queries have been added with this release.
CodeQL CLI¶ Potentially Breaking Changes¶The legacy option --search-path will now be used, if provided, when searching for the dependencies of packages that have no lock file.
CodeQL query packs that specify their dependencies using the legacy libraryPathDependencies property in qlpack.yml/codeql-pack.yml files are no longer permitted to contain a codeql-pack.lock.yml lock file. This will lead to a compilation error. This change is intended to prevent confusing behavior arising from a mix of legacy (unversioned) and modern (versioned) package dependencies. To fix this error, either delete the lock file, or convert libraryPathDependencies to dependencies.
CodeQL CLI commands that create packages or update package lock files, such as codeql pack publish and codeql pack create, will no longer work on query packs that specify their dependencies using the legacy libraryPathDependencies property. To fix this error, convert libraryPathDependencies to dependencies.
Fixed super calls on final base classes (or final aliases) so that they are now dispatched the same way as super calls on instanceof supertypes.
Fixed a bug where running codeql database finalize with a large number of threads would fail due to running out of file descriptors.
Fixed a bug where codeql database create --overwrite would not work with database clusters.
Fixed a bug where the CodeQL documentation coverage statistics were incorrect.
Fixed a bug where the generated CodeQL libarary documentation could generate invalid uris on windows.
Missing override annotations on class member predicates now raise errors rather than warnings. This is to avoid confusion with the shadowing behaviour in the presence of final member predicates.
class Foo extends Base {
final predicate foo() { ... }
predicate bar() { ... }
}
class Bar extends Foo {
// This method shadows Foo::foo.
predicate foo() { ... }
// This used to override Foo::bar with a warning, now raises error.
predicate bar() { ... }
}
Unqualified imports can now be marked as deprecated to indicate that the import may be removed in the future. Usage of names only reachable through deprecated imports will generate deprecation warnings.
Classes declared inside a parameterized modules can final extend parameters of the module as well as types that are declared outside the parameterized module.
Fields are fully functional when extending types from within a module instantiation.
Files with a .yaml extension will now be included in compiled CodeQL packs. Previously, files with this extension were excluded even though .yml files were included.
When interpreting results (e.g., using bqrs interpret or database interpret-results), extra placeholders in alert messages are treated as normal text. Previously, results with more placeholders than placeholder values were skipped.
Windows users of the CodeQL extension for VS Code will see faster start times.
In VS Code, errors in the current file are rechecked when dependencies change.
In VS Code, autocomplete in large QL files is now faster.
Member predicates can shadow final member predicates of the same arity even when the signatures are not fully matching.
The query “Arbitrary file write during zip extraction (“Zip Slip”)” (cs/zipslip) has been renamed to “Arbitrary file access during archive extraction (“Zip Slip”).”
The query “Arbitrary file write during zip extraction (“zip slip”)” (go/zipslip) has been renamed to “Arbitrary file access during archive extraction (“Zip Slip”).”
The query “Arbitrary file write during archive extraction (“Zip Slip”)” (java/zipslip) has been renamed to “Arbitrary file access during archive extraction (“Zip Slip”).”
The query “Arbitrary file write during zip extraction (“Zip Slip”)” (js/zipslip) has been renamed to “Arbitrary file access during archive extraction (“Zip Slip”).”
The query “Arbitrary file write during archive extraction (“Zip Slip”)” (py/zipslip) has been renamed to “Arbitrary file access during archive extraction (“Zip Slip”).”
The experimental query “Arbitrary file write during zipfile/tarfile extraction” (ruby/zipslip) has been renamed to “Arbitrary file access during archive extraction (“Zip Slip”).”
Functions and methods modeled as flow summaries are no longer shown in the path of path-problem queries. This results in more succinct paths for most security queries.
The cpp/comparison-with-wider-type query now correctly handles relational operations on signed operators. As a result the query may find more results.
New models have been added for org.apache.commons.lang.
The query java/unsafe-deserialization has been updated to take into account SerialKiller, a library used to prevent deserialization of arbitrary classes.
Fixed a bug in how map_filter calls are analyzed. Previously, such calls would appear to the return the receiver of the call, but now the return value of the callback is properly taken into account.
Added a new query, cs/web/missing-function-level-access-control, to find instances of missing authorization checks.
The BraceStmt AST node’s AstNode getElement(index) member predicate no longer returns VarDecls after the PatternBindingDecl that declares them. Instead, a new VarDecl getVariable(index) predicate has been introduced for accessing the variables declared in a BraceStmt.
The data flow library now performs type strengthening. This increases precision for all data flow queries by excluding paths that can be inferred to be impossible due to incompatible types.
The data flow library now performs type strengthening. This increases precision for all data flow queries by excluding paths that can be inferred to be impossible due to incompatible types.
Deleted the deprecated getURL predicate from the Container, Folder, and File classes. Use the getLocation predicate instead.
Additional support for command-injection, ldap-injection, log-injection, and url-redirection sink kinds for Models as Data.
When a result of path query flows through a function modeled using DataFlow::FunctionModel or TaintTracking::FunctionModel, the path now includes nodes corresponding to the input and output to the function. This brings it in line with functions modeled using Models-as-Data.
Added automatically-generated dataflow models for javax.portlet.
Added a missing summary model for the method java.net.URL.toString.
Added automatically-generated dataflow models for the following frameworks and libraries:
hudson
jenkins
net.sf.json
stapler
Added more models for the Hudson framework.
Added more models for the Stapler framework.
Added models for the Webix Framework.
Deleted many models that used the old dataflow library, the new models can be found in the python/ql/lib/semmle/python/frameworks folder.
More precise modeling of several container functions (such as sorted, reversed) and methods (such as set.add, list.append).
Added modeling of taint flow through the template argument of flask.render_template_string and flask.stream_template_string.
Deleted many deprecated predicates and classes with uppercase API, HTTP, XSS, SQL, etc. in their names. Use the PascalCased versions instead.
Deleted the deprecated getName() predicate from the Container class, use getAbsolutePath() instead.
Deleted many deprecated module names that started with a lowercase letter, use the versions that start with an uppercase letter instead.
Deleted many deprecated predicates in PointsTo.qll.
Deleted many deprecated files from the semmle.python.security package.
Deleted the deprecated BottleRoutePointToExtension class from Extensions.qll.
Type tracking is now aware of flow summaries. This leads to a richer API graph, and may lead to more results in some queries.
More kinds of rack applications are now recognized.
Rack::Response instances are now recognized as potential responses from rack applications.
HTTP redirect responses from Rack applications are now recognized as a potential sink for open redirect alerts.
Additional sinks for rb/unsafe-deserialization have been added. This includes various methods from the yaml and plist gems, which deserialize YAML and Property List data, respectively.
Added a data flow model for swap(_:_:).
The LogInjection::Configuration taint flow configuration class has been deprecated. Use the LogInjection::Flow module instead.
The ExecCallable class in ExternalProcess.qll has been deprecated.
The Configuration taint flow configuration class from codeql.ruby.security.InsecureDownloadQuery has been deprecated. Use the Flow module instead.
The ProductFlow::StateConfigSig signature now includes default predicates for isBarrier1, isBarrier2, isAdditionalFlowStep1, and isAdditionalFlowStep1. Hence, it is no longer needed to provide none() implementations of these predicates if they are not needed.
It is now possible to specify flow summaries in the format “MyPkg;Member[list_map];Argument[1].ListElement;Argument[0].Parameter[0];value”
Added new libraries Regex.qll and RegexTreeView.qll for reasoning about regular expressions in Swift code and places where they are evaluated.
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