Page 8, found in 55 ms

  1. bounty.github.comhttps://bounty.github.com › researchers › cryptosense
    More about bounty.github.com
    Cryptosense | GitHub Bug Bounty

    … were associated with their GitHub account. These keys were easily factorable and could have allowed an attacker to generate a SSH private key corresponding to the weak public key. To address this …

    0 points
  2. bounty.github.comhttps://bounty.github.com › targets › githubapp-com
    More about bounty.github.com
    *.githubapp.com | GitHub Bug Bounty

    githubapp.com Synopsis Subdomains under *.githubapp.com provide a number of internal services to GitHub employees. These include our internal blog, helpdesk and bastion access to our internal network. Focus areas Authentication bypasses allowing …

    0 points
  3. bounty.github.comhttps://bounty.github.com › researchers › ealf
    More about bounty.github.com
    @ealf | GitHub Bug Bounty

    … included in the next GitHub Enterprise release. @ealf earned an additional 500 points for donating his bounty to a great cause — The Electronic Frontier Foundation . GitHub matches all bounties donated to 501 …

    0 points
  4. bounty.github.comhttps://bounty.github.com › researchers › avlidienbrunn
    More about bounty.github.com
    Mathias Karlsson | GitHub Bug Bounty

    … 01-20-2017 for GitHub CSP 2,500 pts Insufficient OAuth redirect URL validation @avlidienbrunn discovered a flaw in our validation of URLs used for redirection when processing an OAuth authorization request …

    0 points
  5. bounty.github.comhttps://bounty.github.com › researchers › asanso
    More about bounty.github.com
    Antonio Sanso | GitHub Bug Bounty

    … GitHub.com are signed using GitHub’s key. This resulted in GitHub.com signing a commit with its key for an arbitrary, unverified, email address. We addressed this issue by validating the author’s selected email …

    0 points
  6. bounty.github.comhttps://bounty.github.com › researchers › glittershark
    More about bounty.github.com
    Aspen Smith | GitHub Bug Bounty

    … are required for existing GitHub Enterprise releases. The functionality that introduced this issue was not present in any GitHub Enterprise release. Reported on 03-12-2015 for GitHub.com

    0 points
  7. bounty.github.comhttps://bounty.github.com › researchers › x-crossfire
    More about bounty.github.com
    Dmitry | GitHub Bug Bounty

    … responses from internal requests, GitHub addressed the vulnerability by ensuring URLs have an HTTP(S) scheme before making requests. This issue has been fixed in GitHub Enterprise 2.11.0, 2.10.6, 2.9.11, and 2.8.19 …

    0 points
  8. bounty.github.comhttps://bounty.github.com › researchers › brainopener
    More about bounty.github.com
    Mark L. Smith | GitHub Bug Bounty

    … access to repository contents. GitHub addressed this issue by modifying the cache key to only include data from the authenticated user. Reported on 02-11-2017 for GitHub API

    0 points
  9. bounty.github.comhttps://bounty.github.com › researchers › blrhc
    More about bounty.github.com
    Ben Holden-Crowther | GitHub Bug Bounty

    … 08-08-2015 for GitHub Gist 250 pts Insecure content-type detection @blrhc notified us about a potential vulnerability that could allow certain responses from our servers to be treated by the …

    0 points
  10. bounty.github.comhttps://bounty.github.com › researchers › gcanalesb
    More about bounty.github.com
    @gcanalesb | GitHub Bug Bounty

    … processing library used by GitHub Pages. This bug appears to only be exploitable for denial of service. We addressed the bug by using safer functions for handling strings. Reported on 06-21 …

    0 points

Search for “github site:bounty.github.com” on Google, or add !ddg, !w and other shortcuts to any search.