How to pwn a billion dollar VC firm using inspect element
A security researcher found sensitive data from VC firm a16z exposed on their website. Despite the potential risks, a16z didn't offer a bug bounty. The incident stresses the need for responsible disclosure and robust security practices.
Read original articleA security researcher detailed how they discovered sensitive information belonging to a billion-dollar VC firm, a16z, by using inspect element on their website. By scanning subdomains, they found an AWS key exposed in the JavaScript of portfolio.a16z.com, revealing a vast list of credentials including database access, AWS keys, Salesforce details, and more. Despite the real and potentially damaging nature of the credentials, a16z did not offer a bug bounty due to the public disclosure. The researcher attempted to contact a16z but faced challenges finding a suitable contact point. The impact of this security flaw could have compromised PII in the database, AWS resources, Salesforce accounts, and mailgun services. The researcher highlighted the importance of responsible disclosure and expressed disappointment in the lack of a bug bounty reward. The incident gained attention after a TechCrunch article covered the story, emphasizing the significance of proper security measures to prevent such breaches.
Related
Simple ways to find exposed sensitive information
Various methods to find exposed sensitive information are discussed, including search engine dorking, Github searches, and PublicWWW for hardcoded API keys. Risks of misconfigured AWS S3 buckets are highlighted, stressing data confidentiality.
R1 jailbreakers find security flaw in Rabbit's code
A group of R1 jailbreakers discovered a security flaw in Rabbit's code, exposing hardcoded API keys. Rabbit took action after a month, revoking most compromised keys. The breach complicates Rabbit's recovery from R1 AI gadget issues.
OpenAI was hacked year-old breach wasn't reported to the public
Hackers breached OpenAI's internal messaging systems, exposing AI technology details, raising national security concerns. OpenAI enhanced security measures, dismissed a manager, and established a Safety and Security Committee to address the breach.
IdentifyMobile incident exposed 200M records from companies
A security incident at IdentifyMobile exposed 200 million SMS messages from 200+ companies due to an unsecured AWS S3 server. Sensitive data like 2FA codes and transaction numbers were compromised. Investigations are ongoing.
SAPwned: SAP AI vulnerabilities expose customers' cloud environments and privat
The Wiz Research Team identified vulnerabilities in SAP AI Core, enabling unauthorized access to customer data. Reported issues included network bypass, AWS token leaks, and exposure of sensitive information. SAP addressed and resolved all vulnerabilities.
Eva is an incredibly gifted hacker and a responsible one, a16z should treat them better.
We used a nodejs cms called apostrophecms that had an admin panel called global settings.
We used that for managing api keys to our auth server.
We only found out a few months in that it was outputted in the html source code. They did this so it was available to JS, of course it was in their docs. So not blaming them. We glossed over it.
Annoyingly we paid a reasonable amount of money for a pen test with one of the big consultancy companies but they also didn’t see it.
I ended up finding it and checking the logs seems like it wasn’t abused but it was shocking and a big leak
How was such vuln not found and abused in this case? a16z is very lucky or maybe it was abused and not disclosed. Researcher or bored person with a kind heart/white hat hacker mindset is the first to reach out.
a16z should be fined heavily unfortunately there is no legal framework for this type of negligence
That's a clever lifehack to save your company money, by not having any way to privately contact engineering all bug bounties will have to be reported publicly which means you don't need to pay anything.
while the world burns with botched software updates.
I just don't understand this petty attitude. This almost guarantees next time somebody that finds vulnerability with a16z or any of its companies to seek black market rewards that will do far more damage.
This is just like when KakaoTalk refused to payout bug bounty because you had to be a Korean citizen which ended up causing more vulnerabilities to be discovered in the wild.
Companies and billionaires reading this, please don't be petty like Andreesen. Guy went from a leader to a borderline security fraud artist. You don't want to be earning more ire from the public in the current political climate. It's dangerous.
> “On June 30th, a16z addressed a misconfiguration in a web app that is used for the specific use case of updating publicly available information on our website such as company logos and social media profiles. The issue was resolved quickly and no sensitive data was compromised,”
What the fuck is this? They are blatantly lying here. There was a lot of sensitive data compromised. Anyone who inspected the site could have had access to everyones emails.
https://en.wikipedia.org/wiki/Neko_%28software%29
The Wikipedia article is missing the implementation in the article. Too bad they don't pay bounties.
^ ^
0 -
*
-
What is best practice here? Do you first tell the company that they have a security issue, ask for bounty and then help? Is that unethical? Blackmail?
Means what exactly? What information did your public reach-out include?
EDIT:
Ah, I think it's a tweet that said:
> someone from @a16z get in touch, now. its bad. security related.
Lol, ok. I guess they don't want anyone to know they had a security vuln. I wonder if they make you sign an NDA too when you get the bounty.
1. "Surprise pentests" are illegal in the US and pretty much every jurisdiction in the world. If you are actively breaking into websites without a prior agreement, you are not doing anyone a favor. Save your efforts for companies that actually want you.
2. If the company doesn't have a published bug bounty program, they don't owe you anything. Yes they can still be nice and pay you, but they definitely won't if you disclose the vulnerability to the rest of the world without giving them a heads up and enough time to fix it.
3. "Oh I couldn't find an email address" is the worst excuse in the world. I found one after exactly 5 seconds of Googling (at the bottom of https://a16z.com/connect). And even otherwise there's Twitter, Instagram, LinkedIn and a hundred other ways to reach someone at the company if you really want to.
This is classic case of clout chasing over responsible disclosure.
>a16z did not give me any bug bounty on this because of the fact i publicly reached out instead of trying to reach out privately. the only reason i did it this way was because:
> there was no available contact on their main site
> the email i could find engineering@a16z.com bounced my emails
The age-old practice of screwing over security researchers over any possible technicality is still alive and well. Brings tears to my eyes.Finding random email addresses and sending them a notice would have gone no where other than spam folders. I get dozens of "disclosures" every week from mostly script kiddies that think my DKIM setting is somehow going to be the end of my business. My brain automatically ignores emails like it.
Surely any contact would have sufficed to at least try to get an introduction to their security team?
If you browse their website there are loads of email addresses for various offices and divisions.
Related
Simple ways to find exposed sensitive information
Various methods to find exposed sensitive information are discussed, including search engine dorking, Github searches, and PublicWWW for hardcoded API keys. Risks of misconfigured AWS S3 buckets are highlighted, stressing data confidentiality.
R1 jailbreakers find security flaw in Rabbit's code
A group of R1 jailbreakers discovered a security flaw in Rabbit's code, exposing hardcoded API keys. Rabbit took action after a month, revoking most compromised keys. The breach complicates Rabbit's recovery from R1 AI gadget issues.
OpenAI was hacked year-old breach wasn't reported to the public
Hackers breached OpenAI's internal messaging systems, exposing AI technology details, raising national security concerns. OpenAI enhanced security measures, dismissed a manager, and established a Safety and Security Committee to address the breach.
IdentifyMobile incident exposed 200M records from companies
A security incident at IdentifyMobile exposed 200 million SMS messages from 200+ companies due to an unsecured AWS S3 server. Sensitive data like 2FA codes and transaction numbers were compromised. Investigations are ongoing.
SAPwned: SAP AI vulnerabilities expose customers' cloud environments and privat
The Wiz Research Team identified vulnerabilities in SAP AI Core, enabling unauthorized access to customer data. Reported issues included network bypass, AWS token leaks, and exposure of sensitive information. SAP addressed and resolved all vulnerabilities.