Skip to content

fix(security): validate KAITO service ports - #2449

Merged
Tatsat (Tats) Mishra 🐉 (Tatsinnit) merged 1 commit into
Azure:mainfrom
bosesuneha:fix/kaito-service-port-validation
Oct 22, 2026
Merged

Tatsat (Tats) Mishra 🐉 (Tatsinnit) merged 1 commit into
Azure:mainfrom
bosesuneha:fix/kaito-service-port-validation

Conversation

@bosesuneha

Copy link
Copy Markdown
Member

Summary

  • Accept only service ports from 1 to 65535
  • Stop before terminal creation for invalid cluster output
  • Add command injection regression tests

Testing

  • npm test
  • npm run webpack

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for tightening this security boundary and for adding focused regression coverage. I took a pass through the parsing and port-forward flow, and the cluster-supplied value is now normalized and range-checked before it can reach the terminal command. The tests and CI look good to me. Nice, focused fix!

@Tatsinnit
Tatsat (Tats) Mishra 🐉 (Tatsinnit) merged commit 216420f into Azure:main Oct 22, 2026
11 checks passed
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.

2 participants