Text of bounty.github.com › researchers › ChALkeR.html as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout.

Open the live page

Nikita Skovoroda | GitHub Bug Bounty

3,500 pts Nikita Skovoroda @ChALkeR Earned badges Missing Function Level Access Control Cross-Site Scripting (XSS) Reported vulnerabilities 2,500 pts User-controlled `class` attribute on some Markdown tags @ChALkeR discovered that our HTML sanitization library was allowing arbitrary user-controlled class attributes on <code> elements. Our JavaScript relies heavily on this attribute for identifying elements within the page.

Once an element is found, our JavaScript might do a wide variety of things, such as making XHR requests to a URL specified within the tag or performing some same-site action on a resource specified by another attribute in the element. Given the variety of possible impacts of user-controlled class attributes, we worked under the assumption that this bug’s impact was the same as CSRF. We identified that the bug was a regression introduced several months ago.

During our investigation, we found a similar regression affecting another element. We addressed the vulnerabilities by removing the class attribute from the HTML sanitization allowlist for the affected elements. We have added integration and linting tests to ensure that similar bugs are not introduced and that changes to these allowlists receive further scrutiny from our security team in the future. Fixes for this bug were included in GitHub Enterprise versions 2.6.19 , 2.7.14 , 2.8.10 , and 2.9.2 .

Reported on 03-21-2017 for GitHub.com 1,000 pts Issue and pull request title disclosure via comment editing @ChALkeR reported that titles of private issues and pull requests could be disclosed by editing comments made by other users. If a user posted a comment to a repository, an administrative user of that repository could edit their comment and disclose titles using the permissions of the original commenting user. We fixed this issue by changing how tooltips for cross-reference links are resolved and cached.

Reported on 10-15-2015 for GitHub.com