Repository navigation
SONARJAVA-7350 S5542 should not raise on AESWrap and AESWrapPad transformations - #6523
Luqmansonar wants to merge 2 commits into
Conversation
…formations Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
… algorithm Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Code Review ✅ Approved 🟡 Medium risk 1 closed / 1 findingsExempting AESWrap-prefixed transformations from S5542 could suppress warnings for configurations the rule would otherwise flag. Exempts AESWrap and AESWrapPad transformations (and their _128/_192/_256 variants) from S5542, since these JCA key-wrap algorithms do not follow the algo/mode/padding pattern. Explicit AESWrap/ECB/NoPadding still raises as insecure ECB, which was addressed in this session. ✅ 1 closed✅ Edge Case: Explicit AESWrap/ECB/NoPadding transformation still raises as insecure ECB
Verification Rules 2/2 met Repos 4 inspectedFunctional validation No results Rules 2 passed 2 not applicable
Broader impact Repos 4 inspectedCross-repo 4 repositories inspected 0 open impacts
Auto-approval Not enabledFor more verification details, comment OptionsAuto-apply is off → Gitar will not commit updates to this branch. Comment with these commands to change the behavior for this request:
Was this helpful? React with 👍 / 👎 | Gitar |
|




Fixes SONARJAVA-7350.
S5542 reported `AESWrap`, `AESWrapPad` and their `_128/_192/_256` variants because they do not match `algo/mode/padding`. These are JCA key-wrap algorithms (RFC 3394 / 5649), not bulk-data AES without a mode.
Ruling tests were not run locally.
🤖 Generated with Claude Code