156 points morpheuskafka 3 hours ago 15 comments
Besides the PDF processing value add, Cloudinary effectively acts like S3 here, serving assets directly to the web client. Like S3, it has support for signed/expiring URLs. However, Fiverr opted to use public URLs, not signed ones, for sensitive client-worker communication.
Moreover, it seems like they may be serving public HTML somewhere that links to these files. As a result, hundreds are in Google search results, many containing PII.
Example query: site:fiverr-res.cloudinary.com form 1040
In fact, Fiverr actively buys Google Ads for keywords like "form 1234 filing" despite knowing that it does not adequately secure the resulting work product, causing the preparer to violate the GLBA/FTC Safeguards Rule.
Responsible Disclosure Note -- 40 days have passed since this was notified to the designated vulnerability email (security@fiverr.com). The security team did not reply. Therefore, this is being made public as it doesn't seem eligible for CVE/CERT processing as it is not really a code vulnerability, and I don't know anyone else who would care about it.
mtmail 2 hours ago | parent
https://www.fiverr.com/.well-known/security.txt only has "Contact: security@fiverr.com" and in their help pages they say "Fiverr operates a Bug Bounty program in collaboration with BugCrowd. If you discover a vulnerability, please reach out to security@fiverr.com to receive information about how to participate in our program."
wxw 2 hours ago | parent
mraza007 2 hours ago | parent
BoredPositron 1 hour ago | parent
popalchemist 1 hour ago | parent
smashah 58 minutes ago | parent
iwontberude 54 minutes ago | parent
impish9208 43 minutes ago | parent
onraglanroad 35 minutes ago | parent
johnmlussier 29 minutes ago | parent
This is bad.
morpheuskafka 21 minutes ago | parent
(Fiverr itself uses Bugcrowd but is private, having to first email their SOC as I did.)
janoelze 11 minutes ago | parent
mpeg 9 minutes ago | parent
qingcharles 6 minutes ago | parent