bugfix: Initialize Encoder property in the Client Side Control Challenge #54

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open

ProfXwing wants to merge 1 commit into webpwnized:main from ProfXwing:fix/encoder-clientside-control

ProfXwing commented Mar 4, 2025

Currently, the constructor of the client side control challenge creates a local Encoder variable, rather than setting the class's property.

This is breaking for security level 5, which uses HTML encoding for the output.

Setting the class's Encoder property instead fixes this.


          fix: Initialize Encoder property correctly

aaaf00f

sonarqubecloud bot commented Mar 4, 2025

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet