Prevent XSS from Confidant API call

Impact

What kind of vulnerability is it? Who is impacted? Potential XSS from API calls below: GET /v1/credentials GET /v1/credentials/ GET /v1/archive/credentials/ GET /v1/archive/credentials POST /v1/credentials PUT /v1/credentials/ PUT /v1/credentials//<to_revision>

GET /v1/services GET /v1/services/ GET /v1/archive/services/ GET /v1/archive/services PUT /v1/services/ PUT /v1/services//<to_revision>

Stored XSS that can only be used as a stored HTML injection. The attacker needs to be authenticated and have privileges to create new credentials, but could use this to show information and run scripts to other users into the same Confidant instance.

Patches

Has the problem been patched? What versions should users upgrade to? yes, version 6.6.2

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading? NO

References

Are there any links users can visit to find out more? https://hackerone.com/reports/2332004 https://hackerone.com/reports/2456673 https://hackerone.com/reports/2476542 Acknowledgement: Thank you Rein Daelman (trein) for reporting and proposing the fix.