[java] HardCodedCryptoKey: NPE when constants from parent class are used #6191
      
        
          +31
        
        
          −2
        
        
          
        
      
    
  
  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.
  
    
  
    
Describe the PR
Rule: HardCodedCryptoKey
Adds a null check in case the accessed field is not defined in the current class. When the null check fails, check if the field is a compile time constant.
The changed code is shared with
InsecureCryptoIv, the fix applies to both rules.For reference, the fixed NPE stacktrace
Related issues
reported in discussion #6186
Ready?
./mvnw clean verifypasses (checked automatically by github actions)