316

https://konto.zssk.sk/zk/new#step1

Also, it only seems to show "Strong password" if any of these characters is used: !@#$%^&*, and not other special characters.

top 50 comments
sorted by: hot top new old
[-] cmnybo@discuss.tchncs.de 116 points 1 week ago

When they don't allow certain characters in the password, it makes you wonder if they are not hashing the passwords.

[-] farmgineer@nord.pub 84 points 1 week ago

They're probably also not escaping/sanitizing input at all which is also super concerning.

[-] Quokka@quokk.au 17 points 1 week ago

Wonder if the username Bobby Tables is taken.

[-] Naich@piefed.world 12 points 1 week ago

Even more concerning if the validation is being done client side.

[-] user224@lemmy.sdf.org 8 points 1 week ago

In this case it would only show the error after submitting the password, though I didn't check the network logs.

[-] MalReynolds@piefed.social 6 points 1 week ago

Here to say sanitize your inputs Bobby, but you got it covered fam. Cheers.

[-] dan@upvote.au 5 points 1 week ago

My guess would be that they are sanitizing them, but their WAF blocks requests with particular characters in these fields in order to try and block SQL injection or something.

[-] user224@lemmy.sdf.org 32 points 1 week ago

My bank doesn't support any special characters in the password, and letters are case-insensitive. At least the limit is 30 characters, so that's still good enough. Though I really wonder what kind of system doesn't differentiate uppercase and lowercase letters.

Yet, somehow, they did implement OpenPGP for e-mail signing and encryption.

[-] dual_sport_dork@lemmy.world 32 points 1 week ago

Most MySQL/MariaDB collations are explicitly case insensitive (and optionally but very commonly blind to diacritics and accent marks). Your bank is obviously doing queries against a plain text database column.

[-] dan@upvote.au 7 points 1 week ago* (last edited 1 week ago)

Unfortunately there's a huge number of MySQL servers that are using latin1 charset and collation, even when storing Unicode data. Surprisingly it "works" as long as your DB client treats the data as raw bytes (ie you don't do any sort of string manipulation in MySQL), the same way that UTF-8 "works" in PHP even though native strings are just raw bytes.

,Obviously sorting and filtering won't take any sort of case insensitivity / case folding into account though, which is an issue.

I hit issues with this recently at work, because for some reason all our MySQL servers still use latin1 by default. Unicode characters were getting corrupted in JSON columns, because MySQL forces them to use utf8mb4 as per the JSON spec (JSON sent between multiple systems should always be encoded as UTF-8), and mixing "real UTF-8" with "fake UTF-8" (UTF-8 in latin1) doesnt end well.

[-] KickMeElmo@sopuli.xyz 23 points 1 week ago

What's worse is when they allow the backslash but you have to escape the backslash when you actually enter your password to log in.

load more comments (1 replies)
[-] anewfox@lemmy.zip 23 points 1 week ago* (last edited 1 week ago)

it's worse. they're not even using query binding, they're just sticking the password into sql. a bound query would escape these characters properly, a raw query will just accept them as-is. they have a couple steps before they even get to hashing.

[-] h3ll3rsh4nks@ani.social 67 points 1 week ago

That and maximum character limits of 12-20 are insane to me

[-] spicytuna62@lemmy.world 14 points 1 week ago* (last edited 1 week ago)

How large is the file a password is stored on? Can't be more than a few kB. You could probably store the plaintext passwords of literally every Facebook account on one reasonably sized hard disk. There's no reason we couldn't use 500-character passwords if we wanted. A handful of my passwords are over 1,000 characters.

I'd reckon extreme length is much more effective for security than special characters. I'd reckon

1TimewhenIwasatBandCamp,Istuckafluteinmyflutecase

is significantly more secure than any password 8 characters in length for any aspiring flautist.

[-] lagg_mine@lemmy.world 2 points 5 days ago

If you hash a password it'll be a couple dozen base64 characters. All hashes should be the same length.

[-] Gutek8134@lemmy.world 31 points 1 week ago

If the password is hashed (it should), it'd always be the same length, and original's length would only impact how long hashing would take

[-] Pechente@feddit.org 11 points 1 week ago

Exactly that’s why these limits are so stupid. Companies that limit passwords to only a few characters almost certainly have bad security practices.

load more comments (1 replies)
[-] TropicalDingdong@lemmy.world 4 points 1 week ago

So we're calling it a flute case now...

load more comments (1 replies)
[-] excess0680@lemmy.world 8 points 1 week ago

One of the most egregious cases of password length requirements I’ve ever experienced was for the Shinkansen booking website. Now, I acknowledge that it was probably possible to enter hiragana, katakana, or kanji, but for everyone that depends on the Latin alphabet the possible entropy for the password would be abysmal. The maximum password length is

Tap for spoiler8

[-] dan@upvote.au 10 points 1 week ago

One of the big four banks in Australia (Westpac) used to limit you to a password of EXACTLY 6 characters, case insensitive. Another one (NAB) required 6 to 8 characters, case insensitive, with NO special characters.

Thankfully they've both changed these limits.

NAB no longer has a length limit, and they're actually planning on completely removing passwords in favour of passkeys. Westpac allow up to 30 characters now.

load more comments (2 replies)
[-] call_me_xale@lemmy.zip 62 points 1 week ago

"Tell me you're not sanitizing your inputs without telling me you're not sanitizing your inputs."

lol seriously, that is wild. Basically asking to be exploited.

[-] poolcritter@pawb.social 6 points 1 week ago

Neither sanitizing nor even hashing. Hashes don't care what you put in.

[-] homura1650@lemmy.world 4 points 1 week ago* (last edited 1 week ago)

That depends on how you are hashing. If you are doing something like 'os.shell("echo {password} | sha512sum")', you still have to be worried about special characters.

[-] poolcritter@pawb.social 7 points 1 week ago

I don't know whether to be more scared of the fact that people would do this or that people probably have done this.

[-] homura1650@lemmy.world 7 points 1 week ago

I've had to clean up from people doing that. As a bonus, that echo shoved a newline to the end every password.

[-] shalafi@lemmy.world 5 points 1 week ago

I'm no guru, but I know enough SQL Server to know this shouldn't be a big deal to work around.

[-] echodot@feddit.uk 4 points 1 week ago

You get this sort of thing as lesson one in a cyber security course. This is so weak sauce that if they had this on the final exam it would be a joke.

load more comments (1 replies)
[-] cass1312@piefed.blahaj.zone 46 points 1 week ago

The fact its specifically "" and ";" makes it seem really likely they're worried about SQL injections, meaning they must be using a super insecure SQL library and also sticking the password directly in the SQL query (so definitely no hashing)

[-] aksdb@lemmy.world 21 points 1 week ago

It’s also possible those are historically grown requirements they implemented over time without reviewing if older requirements still make sense.

[-] dan@upvote.au 5 points 1 week ago

My guess is that it's not a vulnerability but their WAF still flags/blocks it so they don't want people using those characters.

load more comments (3 replies)
[-] OwOarchist@pawb.social 26 points 1 week ago

AKA, here are the characters you can use to do a form injection on our website.

[-] aeronmelon@lemmy.world 25 points 1 week ago

Little Bobby Drop Tables has a difficult life.

[-] portuga@lemmy.world 21 points 1 week ago* (last edited 1 week ago)

Can I take the opportunity to ask a question?

I work at multinational EU company, we run windows/office for the enduser. There are many parallel systems, some running linux or whatever but that’s besides the point

But there was this audit, performed by an external company, at request of the holding (mother company) that revealed unsafe passwords that contained company name in it. According to the auditors that’s a big no no

My question is: how tf do they even find out that the passwords have some specific string in it? Is it not being salted? That would surprise as our IT/network management team is very capable, and relies on windows tools that should be safe to begin

Just how?

[-] user224@lemmy.sdf.org 26 points 1 week ago
[-] shalafi@lemmy.world 5 points 1 week ago

I would bypass anyone trying to agree and go straight to the CEO or president. How does this person have "security" in their title?!

load more comments (1 replies)
[-] nsns@lemmy.world 15 points 1 week ago* (last edited 1 week ago)

My guesses would be that either:

  • They conducted an employee survey where someone admitted the company name being a substring of a password they use.
  • They used some rudimentary bruteforce methods which matched salted registers or logins (say "Company name123456".)
  • Instead they meant that it is possible to create passwords with the company name in it, but transmitted it poorly.
  • Some of the passwords are unsalted.
  • The passwords are logged somewhere else.

It goes without saying that if they found a vulnerability with the hashing or salting, it should be highlighted on its own, and in any case it wouldn't do damage to ask them directly.

[-] emeralddawn45@lemmy.dbzer0.com 9 points 1 week ago

Or a fake phishing company email that asked employees to log in. That would expose employees who were a high security risk as well.

load more comments (1 replies)
[-] portuga@lemmy.world 4 points 1 week ago

Thanks, it’s probably a combination of the above or even all of them

And like another user shared, they may just be idiots

I just wanted to confirm, there must be plain text databases, they got access to, maybe from some of the less secure systems, on the shop floor or wherever that may have unsecured protocols (they’re inside the corporate network, not directly connected to the internet)

But I’m going with idiots

[-] mlg@lemmy.world 4 points 1 week ago

They could have cracked the password hashes, most likely collected NetNTLMv2 hashes, using a generated list of weak passwords using the company name + a possible ruleset with hashcat.

Some audits still do it against all NTLM hashes stored on the AD DC, but it fell a bit out of fashion because most orgs don't feel comfortable giving out that data for a pentest.

NetNTLMv2 and NTLM hashes are also still notoriously easy to run dictionary and combo bruteforce attacks on with GPUs.

You can see the benchmark for an RTX 5090 here: https://gist.github.com/Chick3nman/09bac0775e6393468c2925c1e1363d5c

It can do a whopping 340.1 GH/s for NTLM and 16017.9 MH/s for NetNTLMv2

Compare that to a Linux's default yescrypt which didn't even have official support in hashcat until this year because the hashrate would be a measly 70-200 H/s.

load more comments (4 replies)
load more comments (1 replies)
[-] Treczoks@lemmy.world 10 points 1 week ago

Yep. I've even seen a German federal system croaking on German umlauts (äöü, etc), without being more specific that "something went wrong".

[-] nightlily@leminal.space 5 points 1 week ago

Etc!? Shit, this guy know about the secret fourth umlaut.

[-] SeventySeven@sh.itjust.works 5 points 1 week ago

I get unreasonably angry when a program only says "Something went wrong."

Bitch, tell me WHAT went wrong then. I can probably fix it on my end, or at least know what to tell someone who does!

[-] Kolanaki@pawb.social 6 points 1 week ago

Ȟ̵̯͉͖̼̝͓͔̗̬͇̜̜̜̽̄̅͐̅̃̊̀͆̆͌̅̍̈̅̾̄͛̍͆̓͑͌͆̒̊̂̈̋̍̐̐̾̀̀̉̓̓̕͘̕͝ṵ̸̧̧̡̢̢̧͇͇̙͇̬̳̣̺͇̳̖̗̪̖̤͇͇̙̗̜͈̫̠̖̻͖͙̗̘͍̠͓̫̯̳̦̼̩͈͇̑̂̑̈̈̈́̓͗̈́̍̀̑̐̀͂͒͐̓̽́͛̏̈́̈͒̀̎̆̂̍͐̚͘̚͜͝ͅͅn̸͙͔̮̝̭̅̓̏͝ţ̵̧̧̡̟̯̭͔̼̖͉͔͍̟̞͎̰̪̼̤͈̝̠̜̗̩̬̤̺̗̥̖̽̿̑͂̉̿̓̆̕͠ͅȇ̷̡̢̞̣̪̼̮̖̟̝̼̤͚͍̰͉͉̥̟̹̱̼̮͚̂̂́́͛̆̊̆̀̂̂̄̔͐̆͌̾̌̓͆̇̽͒͘͘̕͜͝͠ͅr̶̨̛͚̳̗̮̟͉̤͎̺̺̮̤̯͇̹̖̮̯̣͔̺͉̝̠̞͇̖̗̮̪͕̗͇̱̣̪̤͎̰̤̻̘̱͈̀̀̄͐̀̊̀͗͑̃̈́̉̈́͋̑̀̇̓̉́̈́͋͑̉̓̏̏̕̕͠ͅ4̷̢̛̰̗͕̻̭͎͚̟̤̥̗̙̭͙̎́͊̎͆̍̂̑̄͐̂̈́̋̃͝2̶̢̢̢̛̭̘͍̮̪͇̙̪̠͖̗̟̮͚̙̼̹͈͙̥͓̘̗̾̿̉͌̂͌̽̔̾̿̏̈̿̋̈́͐̔̇͋̏͊̎̒́̏̌́̎͐͘͘̚̕͜͠͠

load more comments (1 replies)
[-] cyberpunk007@lemmy.ca 5 points 1 week ago

I just don't get this. Is it lazy programming? I don't really program anymore and was never much if one, but I though at least some languages ad a concept of taking an input literally allowing special characters without injection or something. Forget what it's called...

[-] purplemonkeymad@programming.dev 7 points 1 week ago

Extremely, the password should not even appear anywhere in a comparison or query. It should be hashed with a salt before being checked. What is even worse is this suggests that they are also using a SQL query via string substitution instead of it being parameterised. Considered a no no with user input.

load more comments (1 replies)
[-] bandwidthcrisis@lemmy.world 4 points 1 week ago* (last edited 1 week ago)

I used a website, (the USCIS), which pointed out that they accepted emojis in the password.

Edit: remembered which site it was. It's mentioned here, although they may have switched to id.me now, so the rules may have changed.

https://www.aila.org/aila-files/83E22577-0F60-4BBA-AF2B-4AECC7F28F5E/23021709.pdf

load more comments
view more: next ›
this post was submitted on 07 Nov 2026
316 points (98.8% liked)

Software Gore

6665 readers
2 users here now

Welcome to /c/SoftwareGore!


This is a community where you can poke fun at nasty software. This community is your go-to destination to look at the most cringe-worthy and facepalm-inducing moments of software gone wrong. Whether it's a user interface that defies all logic, a crash that leaves you in disbelief, silly bugs or glitches that make you go crazy, or an error message that feels like it was written by an unpaid intern, this is the place to see them all!

Remember to read the rules before you make a post or comment!


Community Rules - Click to expand


These rules are subject to change at any time with or without prior notice. (last updated: 7th December 2023 - Introduction of Rule 11 with one sub-rule prohibiting posting of AI content)


  1. This community is a part of the Lemmy.world instance. You must follow its Code of Conduct (https://mastodon.world/about).
  2. Please keep all discussions in English. This makes communication and moderation much easier.
  3. Only post content that's appropriate to this community. Inappropriate posts will be removed.
  4. NSFW content of any kind is not allowed in this community.
  5. Do not create duplicate posts or comments. Such duplicated content will be removed. This also includes spamming.
  6. Do not repost media that has already been posted in the last 30 days. Such reposts will be deleted. Non-original content and reposts from external websites are allowed.
  7. Absolutely no discussion regarding politics are allowed. There are plenty of other places to voice your opinions, but fights regarding your political opinion is the last thing needed in this community.
  8. Keep all discussions civil and lighthearted.
    • Do not promote harmful activities.
    • Don't be a bigot.
    • Hate speech, harassment or discrimination based on one's race, ethnicity, gender, sexuality, religion, beliefs or any other identity is strictly disallowed. Everyone is welcome and encouraged to discuss in this community.
  9. The moderators retain the right to remove any post or comment and ban users/bots that do not necessarily violate these rules if deemed necessary.
  10. At last, use common sense. If you think you shouldn't say something to a person in real life, then don't say it here.
  11. Community specific rules:
    • Posts that contain any AI-related content as the main focus (for example: AI “hallucinations”, repeated words or phrases, different than expected responses, etc.) will be removed. (polled)


You should also check out these awesome communities!


founded 3 years ago
MODERATORS