CodeQL 2.18.3 (2024-08-28)¶
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.18.3 runs a total of 425 security queries when configured with the Default suite (covering 164 CWE). The Extended suite enables an additional 128 queries (covering 34 more CWE). 2 security queries have been added with this release.
CodeQL CLI¶
There are no user-facing CLI changes in this release.
Query Packs¶
Minor Analysis Improvements¶
C/C++¶
- The
cpp/uncontrolled-allocation-size(“Uncontrolled allocation size”) query now considers arithmetic operations that might reduce the size of user input as a barrier. The query therefore produces fewer false positive results.
C#¶
- Attributes in the
System.Runtime.CompilerServicesnamespace are ignored when checking if a declaration requires documentation comments. - C# build-mode
noneanalyses now report a warning on the CodeQL status page when there are significant analysis problems – defined as 5% of expressions lacking a type, or 5% of call targets being unknown. Other messages reported on the status page are downgraded from warnings to notes and so are less prominent, but are still available for review.
JavaScript/TypeScript¶
- Message events in the browser are now properly classified as client-side taint sources. Previously they were incorrectly classified as server-side taint sources, which resulted in some alerts being reported by the wrong query, such as server-side URL redirection instead of client-side URL redirection.
Swift¶
- False positive results from the
swift/cleartext-transmission(“Cleartext transmission of sensitive information”) query involvingtel:,mailto:and similar URLs have been fixed.
Language Libraries¶
Bug Fixes¶
Golang¶
- Fixed an issue where
io/ioutil.WriteFile’s non-path arguments incorrectly generatedgo/path-injectionalerts when untrusted data was written to a file, or controlled the file’s mode.
Java/Kotlin¶
- Fixed an issue where analysis in
build-mode: nonemay very occasionally throw aCoderMalfunctionErrorwhile resolving dependencies provided by a build system (Maven or Gradle), which could cause some dependency resolution and consequently alerts to vary unpredictably from one run to another. - Fixed an issue where Java analysis in
build-mode: nonewould fail to resolve dependencies using theexecutable-warMaven artifact type. - Fixed an issue where analysis in
build-mode: nonemay fail to resolve dependencies of Gradle projects where the dependency uses a non-empty artifact classifier – for example,someproject-1.2.3-tests.jar, which has the classifiertests.
Major Analysis Improvements¶
C#¶
- Added support for data flow through side-effects on static fields. For example, when a static field containing an array is updated.
Minor Analysis Improvements¶
C#¶
- Added some new
localsource models. Most prominentlySystem.IO.Path.GetTempPathandSystem.Environment.GetFolderPath. This might produce more alerts, if thelocalthreat model is enabled. - The extractor has been changed to not skip source files that have already been seen. This has an impact on source files that are compiled multiple times in the build process. Source files with conditional compilation preprocessor directives (such as
#if) are now extracted for each set of preprocessor symbols that are used during the build process.
Java/Kotlin¶
- Threat-model for
System.inchanged fromcommandargsto newly createdstdin(both subgroups oflocal).