lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 14 Mar 2014 10:09:25 +0000
From: Pedro Ribeiro <>
To: "Nicholas Lemonias." <>
Subject: Re: Google vulnerabilities with PoC

On 13 Mar 2014 14:30, "Nicholas Lemonias." <>
> I suggest you to read on Content Delivery Network Architectures .
> populates and distributes stored files to multiple servers
> through a CDN (Content Delivery Architecture), where each video uses more
> than one machine (hosted by a cluster). Less populated video files are
> normally stored in various colocation sites. The YouTube architecture uses
> databases for storing metadata information of all uploaded files.

Being a CDN means it is very hard to find out where your file went.

I agree with was said on this thread by other people.

As an external penetration testing consultant, I would put this on a client
report as a low risk finding / possible vulnerability and recommend it to
be fixed.

As an internal vulnerability manager I would push the developers to fix it,
but I would give it a low priority and only real press then once all the
higher priority ones have been fixed.

However in the "real world" it is not a vulnerability, and don't expect
Google to pay you for it.


Content of type "text/html" skipped

Full-Disclosure - We believe in it.
Hosted and sponsored by Secunia -

Powered by blists - more mailing lists