Fix nil pointer dereference in netd IPTables error handling #473
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.
Overview
This PR fixes a crash in
netdcaused by unsafe handling of errors returned fromiptablesoperations.Previously, code paths in
IPTablesRuleConfig.Ensureassumed all errors fromAppendUniqueandDeletewould be of type*iptables.Error.If the error was not (e.g.
exec.ExitErroror another Go error type), the type assertion failed, leavingeerr == nil.The code still attempted to call
eerr.Error()oreerr.ExitStatus(), resulting in a panic:Root Cause
!okwith calls to methods oneerr.!ok,eerris nil, so dereferencing it caused a panic.Fix
ExitStatus()orError()when the type assertion succeeds.*iptables.Error, bubble it up cleanly instead of attempting to interpret it.Impact
netdfrom crashing on unexpected iptables error types.Before
!okbranch still tried to dereferenceeerr, leading to panic.After
*iptables.Errorwith exit status logic.Testing