Skip to content
View in the app

A better way to browse. Learn more.

Web Designer Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Security

Featured Replies

My entire background of web design and programming stems back to my int rest in hacking when I was a little pranksters back in the day (I'm not old... back in the day was a few years ago..)

 

I'm just interested about how much people here on the forum know regarding to threats such as:

 

- SQL Injection

- Blind SQL Injection

- Password Hash Cracking

- Bruteforce / Dictionary Attacks

- Automated Script Attacks

- Javascript injection

- XSS

- Remote file inclusion

- CLRF

- Etc. Etc.

 

If people don't know to much maybe I could start up an educational topic here relating to different security threats.

 

Note: If you have not heard or prepared for most things above, you're dynamic sites (static sites are usually 100% safe on the programmer/designer level) are probably vulnerable in some way.

 

I'm not saying that I'm an experienced hacker, but I know a bit, and I know many 'seasoned' hackers who are dangerously good at taking the smallest mistake in coding and turning it against you.

 

Alright :) Lets here it, what do you know!

Oh wow you can hack with carriage returns!? Kidding. Never heard of CLRF in that context.

 

When I was a grumpy young teen I did some naughty things which is generally how I picked up on a lot of techniques. I recently created a hash table to recover an alpha-numeric password, that was quite good fun and a decent reminder how easy it is to get pure hashed passwords.

 

Javascript injections are pretty useless these days as any good developer will limit Javascript specifically to client functionality and aesthetics where they can. With the likes of ASP.NET and PHP becoming hugely popular "dangerous" tasks aren't really done in Javascript anymore.

 

A lot of websites are prone to SQL injections and looking at code from projects I've taken people still use SELECT * without a limit in queries for a column or two with no input validation... Ridiculous. If your that careless and lazy it's kind of your own fault on that one.

 

You should definitely start topics and provide information/tutorials though. I can't see it hurting anyone. It's hard to prevent something like an "SQL Injection" when you don't actually know what an "SQL Injection" is. It's also very interesting to learn for new developers.

I have witnessed and actually seen how SQL Injection works. Man is it an eye-opener when you discover how easily you can take over a website if the programmer is not careful. Especially those ones with back end admin interfaces. Every single input can be used against you if you don't cleanse them of dangerous symbols. URL Inputs, Form Inputs...

 

I actually face the problem of trying to come up with ways to allow users to add video embeds without fear an attacker. If I just left the input wide open, problem solved, but I also left the front door wide open...There are so many video embed codes out there with variations on parameters...so how do you clean that stuff before submitting the info??

 

I'm new to this whole security thing. I want to learn more about it - awareness.

This is a great topic to cover we should all try and contribute.

 

I'm currently developing a new site with an admin section which hopefully will not be vulnerable to the mentioned types of attacks.

 

For most input screening, regular expressions come in handy because you can accept only the data you want and discard the rest.

  • Author
Oh wow you can hack with carriage returns!? Kidding. Never heard of CLRF in that context.

 

Oh yeah, its very situational, but it can be done, and it can be done well..

 

Say you have a plain text feed of a little "chat box"

 

Admin: Hey guys I'm signing out for the night.

 

Now the hacker types in his message with a CLRF, there's different ways to get it in there..

 

Hacker: Alright \r\n <b>Admin: Guys quick, go here http://www.attackersite.com/phishingscript.php</b>

 

Now, to the average user it appears like this

 

Admin: Hey guys I'm signing out for the night.

Hacker: Alright

Admin: Guys quick, go here http://www.attackersite.com/phishingscript.php

 

 

...

 

 

Obviously thats very specific, and most sites wouldn't be vulnerable to it even if they didn't know about it, but its all the things that add up, little vulnerabilities here and there that can compromise a site.

 

 

 

About mysql injection, its scary the amount of sites that are vulnerable. I'll look at getting some articles up.

Skysurge, your idea is great, and sharing your knowledge with us will help us for sure

  • Author

Alright when I have some free time I'll put a bunch of stuff together in a new topic, I've got a big project I have to code by friday!

One of you guys wouldn't happen to be testing security on my site would you? I just checked up on it and everything's down...this is what happens when you read too much about security in a week...paranoia.

 

EDIT: (30 minutes later...my my everything is back up...it makes you appreciate the value of data) :)

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.