Repository navigation
fix: skip SSA analysis on ill-typed packages to prevent panic - #1607
Merged
ccojocar merged 1 commit intoMar 13, 2026
Merged
Conversation
Packages with type errors (pkg.IllTyped == true) have partial type information that can cause nil pointer dereferences inside the SSA builder (golang.org/x/tools/go/ssa.emitConv). Add a pkg.IllTyped guard in buildSSA that returns a clean error instead of letting the SSA builder panic. AST-based rules continue to run normally on the affected package. Fixes securego#1604
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1607 +/- ##
=======================================
Coverage 81.01% 81.02%
=======================================
Files 108 108
Lines 10010 10012 +2
=======================================
+ Hits 8110 8112 +2
Misses 1418 1418
Partials 482 482 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Packages with type errors (
pkg.IllTyped == true) have partial type information that can cause nil pointer dereferences inside the SSA builder (golang.org/x/tools/go/ssa.emitConv). This results in a panic duringgosecscans, even though the panic is caught bydefer/recover— users still see a frightening 50+ line stack trace.Root Cause
When
packages.Loadprocesses a package with compilation errors, it still populatespkg.Typesandpkg.TypesInfowith partial data. SomeTypesInfo.Typesentries have nilTypefields for expressions the type checker couldn't resolve. The SSA builder doesn't guard against these nil types inemitConv, causing a nil pointer dereference.The existing guards in
buildSSAcheck forpkg.Types == nilandpkg.TypesInfo == nil, but miss the case where these fields are populated with incomplete data.Fix
Add a
pkg.IllTypedcheck inbuildSSA(after the existing nil guards) that returns a clean error before attempting SSA construction. AST-based rules continue to run normally on the affected package.Before:
After:
Changes
analyzer.go: Addpkg.IllTypedguard inbuildSSAanalyzer_core_internal_test.go: AddTestBuildSSAIllTypedPackageFixes #1604