Skip to content

Conversation

Umbs01
Copy link

@Umbs01 Umbs01 commented Jul 7, 2025

This pull request fixes functions that leak the credentials setting of the Platform Authentication and socks proxy. The issue was reported in #22.

changes:

  • Added Checkbox in the Burpsuite MCP UI to enable the filter.
  • When the filter is on, the password fields in Platform Authentication and socks proxy is changed to "*****".
  • Added unit tests in 'src/test/kotlin/net/portswigger/mcp/security/CredentialFilterTest.kt'.

please review and let me know if there are any issues or improvements needed.

@portswigger-penguin portswigger-penguin self-assigned this Jul 17, 2025
@portswigger-penguin portswigger-penguin self-requested a review July 17, 2025 12:59
Copy link
Collaborator

@portswigger-penguin portswigger-penguin left a comment

Choose a reason for hiding this comment

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

I'm just doing some manual sanity tests and I've left some small change suggestions, but overall looks good and it was a great idea to add this for security.

Assuming the sanity tests work well I'm also happy to get this merged and I can make the cleanup changes done in another PR. Let me know what you'd prefer. 😄

@portswigger-penguin
Copy link
Collaborator

Just did some manual testing. Unfortunately at the moment there are a few issues with the static dataclass schema representation of the Burp project and user settings. I'm thinking that it may be easier to approach and maintain it from a dynamic JSON parsing approach so if changes are made to the Burp settings JSON schema we don't need to make updates. I'm happy to help out with implementing this if you get stuck. Unfortunately I won't be able to get to this until the end of the month though.

@Umbs01
Copy link
Author

Umbs01 commented Jul 21, 2025

Thank you for the feedback! I agree that the static JSON serialization wasn't the best approach. I've committed a new version of the feature using a recursive approach, which should make it more maintainable in case of future changes to the JSON schemas. Feel free to take a look at the changes and let me know if any adjustments are needed.

@Umbs01
Copy link
Author

Umbs01 commented Aug 4, 2025

I'm sorry for the delay, I didn’t catch all of them in the first pass. I’ve gone ahead and fixed the remaining issues on the test module as per your suggestions.
Let me know if there’s anything else you'd like me to tweak.

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