d9eadddfe3
adding flash message with validation errors, and redirect to sign_up
2013-10-07 13:47:33 -04:00
da061c79b6
intended to remove some of the weirdness when updating a users account. A blank password basically ends up causing the previously existing password to be hashed twice. Probably move to has_secure_password at some point although that may end up screwing up the intent of the particular tutorial item
2013-09-30 13:03:03 -04:00
e0bca0139e
Added command injection Capybara spec.
2013-09-27 14:59:30 -05:00
20420be1a6
Fixed logic to strip out user params.
...
Disclaimer: changes like these in this sort of app are tricky because
it's harder to presume the intention of the code in question.
The prior line:
```
user.update_attributes(params[:user].reject { |k| k == ("password" || "password_confirmation") || "user_id" })
```
returns an empty hash, because of the way the block evaluates:
```
irb(main):002:0> k = 'foo'
=> "foo"
irb(main):003:0> k == ("password" || "password_confirmation") || "user_id"
=> "user_id"
```
Before the last change to that line, without 'user_id' outside the
params, it didn't evaluate properly either:
```
irb(main):007:0> k = 'password_confirmation'
=> "password_confirmation"
irb(main):008:0> k == ("password" || "password_confirmation")
=> false
irb(main):009:0> ("password" || "password_confirmation")
=> "password"
```
So, in the normal use case for this form, you can't update any other
attribute of the User. To me, that's probably the best argument for
making this change, but it does simplify the SQL Injection attack
(although perhaps the prior complication was intended).
Before this change, injecting conditional SQL into the user_id param in
the account_settings update call would allow the password of whatever
account is found (e.g. the first one if injecting 'OR 1=1') to be reset,
but without additional attacks, the email address of that account is not
known.
After this change, the email address of that account now is also updated
in addition to the password, making it simpler to get in as an admin --
though you're still presuming the first account to be an admin.
2013-09-25 16:56:34 -05:00
aab489ef40
fix for performance bug
2013-09-10 21:58:29 -04:00
69c180e845
minor changes to spec_helper and user model
2013-09-06 15:54:06 -04:00
65eb2caeaf
made a suggestion based on digininjas comment on Rails tutorials blog post. Better to change method name to hash_password than encrypt_password
2013-08-08 16:57:58 -04:00
f67bd0f5ed
correct naming within the command injection tutorial
2013-07-28 19:44:51 -04:00
14c1fb367d
added a tutorial for command injection
2013-07-10 20:42:04 -04:00
82b5809bee
almost finished with the write-up for the command injection vulnerability
2013-07-10 11:41:36 -04:00
ce6f32a1a2
working command injection in fileupload, closes issue #23
2013-07-09 16:36:03 -04:00
ea2014b637
I have exhausted all thoughts on how to actually get jquery file upload to work, so screw it, I am just going to make something homegrown for tomorrow
2013-07-09 13:53:00 -04:00
1a79471ef8
trying to fix a bug where you have to click twice on the tutorial credentials button
2013-06-20 11:28:29 -04:00
2e052828a6
taskbar / active enhancement
2013-06-16 00:49:28 -04:00
7b900bda2d
fixes issue #24
2013-06-10 16:25:14 -04:00
56381fe318
fixed issue #25
2013-06-10 15:27:21 -04:00
5ea8006fc1
closes issue #22
2013-06-07 09:05:11 -04:00
39d2e9d79f
finished CSRF/AJAX, closes issue #21
2013-06-06 22:40:52 -04:00
d445e59a98
this fixes issue #20 , seriously, no clue how I missed the missing constantize code
2013-06-06 16:43:58 -04:00
9d42453b05
removed pesky files
2013-06-04 16:00:30 -04:00
bdf3f20955
added a license
2013-06-04 14:17:12 -04:00
b76283910c
holding off on the last issue until i confirm whether or not oreoshake can cover secure headers here
2013-06-04 14:06:10 -04:00
bb2985018d
closes issue #7
2013-06-04 13:59:41 -04:00
089e9540ac
finished admin filter and write-up for issue #6
2013-06-04 11:49:59 -04:00
b0ace5ebef
added write-up for issue #8
2013-06-04 11:24:39 -04:00
ef2b2e8e11
okay, finally got a working redirect vuln
2013-06-04 11:00:01 -04:00
e1dfb8309c
finished the write-up for crytpo vuln, close issue #5
2013-06-03 18:08:21 -04:00
0b09e0d4c1
added the primary insecure crypto storage vuln
2013-06-03 12:52:24 -04:00
6d5623a423
changed SQLi vuln location, did write-up, closes issue #1
2013-06-03 12:31:34 -04:00
6528b56de6
added a sql injection vulnerability
2013-06-03 02:19:36 -04:00
2ac771ca50
Issue #3 can be closed, write-up and vuln complete for A4
2013-06-03 01:54:07 -04:00
14251e6f39
added Insecure dor vuln
2013-06-03 01:29:16 -04:00
912c34a26e
finished the writeup for password complexity
2013-06-03 01:11:51 -04:00
88ea613da6
okay, write-up finished
2013-06-02 23:32:37 -04:00
86695e9e07
removed excess commented code
2013-06-02 22:42:50 -04:00
e97afb9bb4
added a very dangerous, very serious vulnerability (constantize
2013-06-02 22:42:29 -04:00
caecb88e30
prepping for constantize
2013-06-02 20:35:01 -04:00
570eafa01b
this closes issue #9
2013-06-02 20:19:31 -04:00
06dce1f8b2
I believe this has resolved the dependent destruction and we can close issue #18
2013-06-02 13:08:56 -04:00
4e445375fa
created the info disclosure write-up. Close issue #16
2013-06-02 12:39:04 -04:00
1267661c6a
seems the signup bug has been fixed, I would close this for now
2013-06-01 19:49:01 -04:00
0319cc4768
added a few things here. Firstly, I fixed the broken delete function with the admin page. Secondly, whenever you register for this application, we will automatically populate your user data to make the application functional. Seemed like the easiest way to do this
2013-06-01 00:19:07 -04:00
38fcc263bd
update account is now an ajax call
2013-05-31 22:10:32 -04:00
417aca2078
keeping changes up to date
2013-05-31 19:55:49 -04:00
6199beb780
we are going to fix this by automatically generating data for ppl that register HOWEVER, just in case that fails for some reason, I have applied a filter that ensures if some data is not associated with a person they cannot navigate to all aspects of the application. This is a preventive measure
2013-05-31 19:02:00 -04:00
c63275b3b3
dashboard figures actually indicate correct values now
2013-05-31 15:54:25 -04:00
3cab9810fc
hehe
2013-05-31 15:22:13 -04:00
4813ba9349
added visualization chart for performance history
2013-05-31 15:20:58 -04:00
379c442049
I have added the performance model, controller, route and seed data, now I am working on the actual visual aspects of the page
2013-05-31 14:45:31 -04:00
2fa68be920
added the last part to the SSN related vuln
2013-05-31 13:59:57 -04:00
Mike McCabe