Jenkins Configuration Issues. Based on the same benchmark, I reported a few vulnerabilities to BlackBerry in its infrastructure. Recently, I found that they added my name to the responsible disclosure list here: BlackBerry Responsible Disclosure List!.which is fine as long as the team eradicates the vulnerability.
Nowadays, I do not perform aggressive vulnerability hunting (due to my ongoing job) but, when I have time, I dissect components of widely used software and try to find flaws in them. I am more interested in the cases where companies understand the problem and ready to patch it. I am not at all inclined towards finding generic issues in websites which nobody cares about. I always believe that it is important to understand the cons associated with that existing vulnerability when it is reported. It is also crucial to determine how the attacker can chain together a set of bugs to have greater impact. If we don't understand the nitty-gritty details of the vulnerability, there is high chances that the vulnerability will resurface again.
In this case of BlackBerry, unnecessary exposure of Jenkins component in production environment could resulted in problematic scenarios. Exposed components of Jenkins were vulnerable to flaws such as Injections, XSS, etc. So, the belief is: "Expose Less and Be Secure !"
Note: I am going to reveal Frame Injection vulnerability to Jenkins team so that the issue can be patched. No details for now.