Skip to content

Conversation

@stevebeattie
Copy link
Member

In commit 3147dd1 ("Update third-party rules as of 2025-01-26 (#780)"), the the YARAForge rule for detecting Eziriz .NET Reactor obfuscated DLLs was renamed from COD3NYM_SUSP_OBF_NET_Reactor_Indicators_Jan24 to COD3NYM_Reactor_Indicators.

However, this rule has a false positive exception because it seems Sonarqube uses this obfuscator on its CSharp and VBWeb plugin DLLs, but the exception rule was not updated at the same time the rule was renamed. Fix that.

[Verified that none of the other rule names in the third-party rules update that changed are referenced in the false_positives directory.]

@stevebeattie
Copy link
Member Author

Example usage where it was flagged without detecting that it was an exception: wolfi-dev/os#41189

In commit 3147dd1 ("Update third-party rules as of
2025-01-26 (chainguard-dev#780)"), the the YARAForge rule for detecting
Eziriz .NET Reactor obfuscated DLLs was renamed from
`COD3NYM_SUSP_OBF_NET_Reactor_Indicators_Jan24` to
`COD3NYM_Reactor_Indicators`.

However, this rule has a false positive exception because it seems
Sonarqube uses this obfuscator on its CSharp and VBWeb plugin DLLs,
but the exception rule was not updated at the same time the rule was
renamed. Fix that.

[Verified that none of the other rule names in the third-party rules
update that changed are referenced in the false_positives directory.]

v2: perform `yr fmt` on the sonarqube.yara file to make the CI happy

Signed-off-by: Steve Beattie <steve.beattie@chainguard.dev>
@stevebeattie
Copy link
Member Author

Fixed in #788, closing.

@stevebeattie stevebeattie deleted the sonarcube_exception branch February 4, 2025 01:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant