Bug in youtube non-skippable ads.
Reported by
aniketsa...@gmail.com,
Oct 10 2016
|
||
Issue descriptionThis template is ONLY for reporting Download Protection Bypass bugs within Chrome and is not for requesting a review of sites or binaries identified as malicious. VERSION Chrome Version: 53.0.2785.143 (64-bit) Operating System: Ubuntu 14.10 REPRODUCTION CASE I have reported this bug to (Jonathan) yt-partner-support@google.com and he accepted that what i reported is a workaround , but when i asked about any kind of bounty, Jonathan asked me to contact someone else so i thought of submitting the report again. I can forward you the copy of email conversation between me and Jonathan, if you need, just email me about it. The steps to reproduce the bug are as follows: lets assume that the url is "https://www.youtube.com/watch?v=someRandomAlp". Now, as soon as you see a Non-skippable ad Steps to follow: 1. Append #t=0 to the url and press enter(Nothing will happen but your current url has became "https://www.youtube.com/watch?v=someRandomAlp#t=0"). 2. now press f5 or reload the page and there you go, Ad has been disappeared :) Sometimes you may need to reload the page twice or thrice till the ad disappears. Browser/OS: I have cross checked in most of the modern browsers with different OS, IT WORKS EVERYWHERE!!! I have attached video while performing the above method. Scenario: An application that appends t=0 can be made. Also if the ad appears in the middle of video, getting url at current time can also work to make ads disappear.
,
Nov 8 2016
This would be a YouTube bug and not a Chrome bug - if a bug bounty is what you're after, I think yt-partner-support@google.com might have been a better contact. Perhaps ask them to be more specific about who you should have contacted instead? From a quick look online though, it doesn't seem like YouTube is covered for regular bug bounties, only for security vulnerabilities, so I'm not sure if you'll have much success with that - I could be wrong though. Closing this as WontFix (not a Chrome bug). |
||
►
Sign in to add a comment |
||
Comment 1 by sureshkumari@chromium.org
, Oct 12 2016Labels: Needs-Feedback OS-Mac OS-Windows