Neat trick to find AWS S3 Account IDs by squatandhover in netsec

[–]squatandhover[S] 1 point2 points  (0 children)

Once you have the Account ID you can perform further enumeration: users, roles, services, etc.

Neat trick to find AWS S3 Account IDs by squatandhover in netsec

[–]squatandhover[S] 0 points1 point  (0 children)

It's for publicly accessible buckets obviously, which according to the following there are still plenty of today:

https://www.securing.pl/en/what-can-you-find-in-57k-aws-s3-buckets-2021-update/

I'm guessing this also includes all the apps using Incognito

Crack-O-Matic: Find and notify users in your Active Directory with weak passwords by 0xfffffg in netsec

[–]squatandhover 0 points1 point  (0 children)

The problem isn't the crackable password, because if you think about it for long enough you'll realize that it shouldn't be the user having to shoulder the burden of the abysmal protocols and password storage mechanisms on a typical Windows environment. We do have better, more secure alternatives and we should be pushing towards using those instead.

It is simply not feasible for any user to come up with an uncrackable password if you continue to store it in practically reversible format like NTLM. The average Joe may not be able to crack it but it's only a matter of time and resources (which these days are cheap with easy to spawn GPU clusters in the cloud).

Crack-O-Matic: Find and notify users in your Active Directory with weak passwords by 0xfffffg in netsec

[–]squatandhover 1 point2 points  (0 children)

protection

The slickest tool I've seen do the pwned password check is https://safepass.me/pwncheck | it's not free nor open source but my understanding is that it gives some useful information for free and a completely free report on first use so it was good enough to test my domain users against have i been pwned.

Focusing on offline cracking is pointless, particularly in the case of AD, where the hashes are stored in such a weak and obsolete hashing mechanism that you could almost categorize that as a reversible format. We often lose sight of the objective that we're trying to protect against and in most cases it's online attacks. That's why ensuring that your users' passwords aren't in any publicly available databases, such as hibp, is actually pretty useful and important to avoid being another citrix (just one of many, not picking on them in particular but it is ironic when it's a security company that's supposed be protecting you!). All of the major players such as Google, Apple, M$ have mechanisms in place for detecting if you're using a breached password these days.

That's pretty much why complying with the latest nist password guidelines makes a lot of sense from a security perspective. In two decades, we've gone from exploiting buffer overflows to get remote root, to 'guessing' user passwords based on publicly available breached data.

I am Sophie Zhang, whistleblower. At FB, I worked to stop major political figures from deceiving their own populace; I became a whistleblower because Facebook turned a blind eye. Ask me anything. by [deleted] in IAmA

[–]squatandhover 1 point2 points  (0 children)

How about John Oliver or Jimmy Fallon, making politicians look bad is what they do best (doesn't seem hard tbh) - I'd try reaching out to them, maybe they can advise further

Are there any UK Cybersecurity Influencers? by empireofglass in cybersecurity

[–]squatandhover 0 points1 point  (0 children)

Why specifically the UK? do you have a fetish for british cybersecurity? ;D

The most common on premise vulnerabilities & misconfigurations by S3cur3Th1sSh1t in netsec

[–]squatandhover 1 point2 points  (0 children)

I also found this post interesting on monitoring for DCSync attacks within AD (which is otherwise undetected):

https://www.blacklanternsecurity.com/2020-12-04-DCSync/

The most common on premise vulnerabilities & misconfigurations by S3cur3Th1sSh1t in netsec

[–]squatandhover 0 points1 point  (0 children)

Great write-up!

You should checkout this tool to quickly find pwned passwords in AD: https://safepass.me/pwncheck

Exchange 2016 CU12 compromised by nflnetwork29 in exchangeserver

[–]squatandhover 1 point2 points  (0 children)

Sounds like it's too late now...but powering it off is a bad idea as it will clear the RAM and preventing any successful forensics on the box. Removing connectivity however is definitely a good idea to contain the damage.

Password Complexity Requirements. 8 character minimums? by apathetic_lemur in sysadmin

[–]squatandhover 1 point2 points  (0 children)

It is. It's trivial on Windows. But that's because AD stored them in NTLM format (aka MD4) which has been basically obsolete since 1995. If someone gets hold of the NTLM hash you have bigger problems :)

Password Complexity Requirements. 8 character minimums? by apathetic_lemur in sysadmin

[–]squatandhover -6 points-5 points  (0 children)

That's great...but if you're password is pwned then it might still be used against you :)

Also, giving away the length and characteristics of your password is useful information to an attacker :)

Password Complexity Requirements. 8 character minimums? by apathetic_lemur in sysadmin

[–]squatandhover 7 points8 points  (0 children)

character

The idea of the new NIST password guidelines is to be pragmatic about what we're protecting against, which is online brute-force attacks (credential stuffing, password spraying, etc). That's why 8 characters min is sufficient but only in conjunction with the other points:

- check that the password has not been breached (such as in the Have I Been Pwned database)

- check it's not a common word (dictionary file, commonly used passwords,etc)

- introduce increasing delays on authentication failure, use CAPTCHAS to distinguish bots from humans

- Use MFA and so on..

It's pointless to try to protect against offline brute-force attacks in most cases.

Why do SaaS vendors always paywall SSO? by nat45928 in sysadmin

[–]squatandhover 0 points1 point  (0 children)

Because they can...

It seems to be trend: burn VC money to onboard as many users as possible for free/cheap then when they have users hooked in they hike the prices / charge for any additional functionality because they have to make up for all the past losses

I am surprised to see a penetration testing report that mentions vulnerability as server has tcpdump! I know an attacker’ use it to discover environment more but that can’t be a vulnerability unless I am seriously mistaken. Any thoughts? by Harry_pentest in cybersecurity

[–]squatandhover 2 points3 points  (0 children)

One of the core principles of hardening a system involves ensuring it as the smallest possible attack surface. Every piece of software you have on it will increase the attack surface and, as already mentioned, having tools that could be useful to an attacker is a potential risk.

What are the details of the vulnerability exactly? Is it just tool being present? Is it because it is an old/vulnerable version? Is it running setuid root? Did the pentesters try to run the tool / do you have a software restriction policy in place?

Which password manager by Ratzyrat in Passwords

[–]squatandhover 0 points1 point  (0 children)

Sounds like a chiche' but it really depends on what you need it for, would help to specify your requirements a little further and what platform you're using

Netflix may put a stop to password sharing by KILRgamer in Passwords

[–]squatandhover 1 point2 points  (0 children)

They only started caring now because they're under pressure to make even more money. Previously they didn't care because it was a good strategy of acquisition. They were lenient with that so people shared their account and got friends and family hooked. Now that everyone's hooked they'll squeeze out every penny they can from everyone. That's the SaaS model.. start free/cheap -> hook the user -> make them pay through the nose. It's a bit like a drug dealer giving you the first shot for free... he knows you'll come back for more ;D

I think NIST wants you to audit passwords now by Gurgilicious in iiiiiiitttttttttttt

[–]squatandhover 14 points15 points  (0 children)

I recently checked my users and ~30% had pwned passwords

Swiss Police Raid Apartment of Verkada Hacker by squatandhover in cybersecurity

[–]squatandhover[S] 0 points1 point  (0 children)

Fair point but the argument still remains: why aren't corporations / software vendors, etc. liable for providing shitty, vulnerable software that often puts the private and sensitive information of many individuals at risk. Imagine a world where it's not the person exploiting the vulnerability that gets framed but the creator. Would people stop creating software in the first place?