"The state’s goal is for citizens to lose one million pounds, and httpx://sanyuwu.com/index.php?top-lesbian-dating-sites-pii the website even suggests ways to get the family dog involved. Trainers and nutritionists will be"
Whats fascinating to me is that the content seems to have been removed from most of these pages. Some staff member is likely manually deleting them and didn't think to escalate the situation
Asking because I had multiple bad experiences with responsible disclosure, yet I do not believe full (public presumably) disclosure is the right initial path.
"Responsible" disclosure at best results in an embargo where "trusted" parties get to sit on it while the general public remains at risk. Worst case you get the cops knocking at your door.
(Full disclosure should be done anonymously to prevent the latter from happening anyway)
Let's say hypothetically someone found this hacked website, sent an e-mail to the site owners' security reporting contact, and after a year they hadn't taken any action.
Some would say a "responsible" disclosure which allows the danger to continue unabated for a year is a greater danger than a public disclosure, which would lead to the danger being fixed.
That is one hypothetical scenario, yes. Another hypothetical scenario is that as a result of responsible disclosure the site owners patch the hole and ensure customer data isn't publicly accessible before the vulnerability is public knowledge.
Seems reckless to me to not even _try_ responsible disclosure. You don't have to wait a year. But at least give a chance for the problem to be solved before you make it common knowledge.
Responsible disclosure creates a ton of perverse incentives for all parties and ultimately leaves customers worse-off. Bug bounty programs and all of the drama and exploitative labor issues fall into this pit.
Full disclosure might have short-term negatives for _companies_ involved but is best for customers/users as it allows them to evaluate and implement their own mitigations as early as possible. It's the only truly ethically consistent way to operate.
This really sounds like you’re back-solving from a pre-existing ideology of complete openness. A customer’s ability act early, e.g. mitigate, is quite clearly context-dependent. I can think of vendors I interface with as a customer that I’d prefer had vulnerabilities ‘responsibly disclosed’ to them. Nothing in technology is this simple. The absolute nature of your claims make it near impossible to actually take this seriously.
Clicking the link from the google search results continues to work, I just tested it on my phone. Visiting the page directly continues to redirect for me
If you think the site is still serving the redirects I’m going to make a phone call to a publicly available number of some Cyber Crime division for Georgia’s GBI.
Worked for me with no changing of any referrer or other HTTP settings. Clicking on the first georgia.gov resulted redirected me to the spam site. (Win11 + Chrome)
referrer google or user agent google bot is a great way to have google specific shenanigans to rank higher in search.
Google says it's against their policy but plenty of sites do that. Plenty of sites let their paywalls down just for GoogleBot to the ranked in search but real users have to pay.
Some sites don't load ad crap to show GoogleBot how fast they are.
What? I have proof it’s not dynamically generated. The rest of the website is powered by Wordpress, but this redirect is entirely powered by Apache. If users can do that, that’s absolutely a problem.
And it absolutely is still there. I’ve clicked the links on a multitude of different browsers, and they continue to work. One comment lead me to discover that it only works if you are referred by google.com: https://shottr.cc/s/1CXn/SCR-20240426-cm4.png
You’re the one who needs to get over yourself. A government website acting as referral spam for over a year is absolutely noteworthy
Assuming you've breached WordPress, and can run arbitrary php, you can produce that kind of result. I think that path is more likely/common.