This repository was archived by the owner on Aug 21, 2025. It is now read-only.
Potential fix for code scanning alert no. 6: Construction of a cookie using user-supplied input #382
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Potential fix for https://github.com/microsoft/AcademicContent/security/code-scanning/6
To fix the problem, we should ensure that the value of
voter_idset in the cookie is not directly taken from user input unless it is validated to be safe. The best way to do this is to validate the format ofvoter_idbefore using it, and if it does not meet the expected criteria (e.g., a hex string of a certain length), generate a new random value instead. This prevents attackers from injecting arbitrary values into the cookie. The change should be made in thehellofunction in archive/Events and Hacks/Tech Talks/ContainerDemo/example-voting-app/vote/app.py, specifically around the logic that retrieves and setsvoter_id. No new imports are needed, as the required modules are already present.Suggested fixes powered by Copilot Autofix. Review carefully before merging.