mirror of
https://github.com/jackyzha0/quartz.git
synced 2025-12-27 06:44:07 -06:00
vault backup: 2022-09-08 18:47:28
This commit is contained in:
parent
b4e0f3bcce
commit
5b02520fd5
@ -6,15 +6,15 @@ tags:
|
||||
- comp210
|
||||
---
|
||||
|
||||
|
||||
# Security Audit for Awesome Web Site
|
||||
Jet Hughes - 9474308
|
||||
|
||||
# Summary of system
|
||||
## Summary of system
|
||||
- function
|
||||
- technology
|
||||
|
||||
# Flaws
|
||||
## SQL Injection
|
||||
## Flaws
|
||||
### SQL Injection
|
||||
CWE: 89
|
||||
|
||||
It is possible to inject SQL into the database using the login username field, and display it in the brower as the "username" of the logged in user.
|
||||
@ -26,9 +26,11 @@ In the username field of the login form I entered the string:
|
||||
|
||||
' union select group_concat(username||':'||password||':'||name||':'||credit_card_number||':'||credit_card_expiry||':'||credit_card_cvv) from user as name;--
|
||||
|
||||
This resulted in all the users data and hashed passwords being displayed in the browser. I was then able to crack 48 of the passwords using hashcat and the rockyou wordlist.
|
||||
This resulted in all the users data, credit card informaton, and hashed passwords being displayed in the browser. I was then able to crack 48 of the passwords using hashcat and the rockyou wordlist.
|
||||
|
||||
## Cross site scripting/Javascript injection
|
||||
An attacker would not know the names of the fields or the tables. However security through obscurity is not sufficient and an attacker could guess or otherwise find the information.
|
||||
|
||||
### Cross site scripting/Javascript injection
|
||||
CWE: 79
|
||||
|
||||
The product catalogue is visible to other users. This means if we were able to update the product information in the database we could run javascript on the brower of other users.
|
||||
@ -41,32 +43,38 @@ An attacker could use this to present the user with an unsafe link, or export da
|
||||
|
||||
I was also able to create an account with the username ''<script>alert("hello")</script>", however when I logged in, the alert was not shown and the username in the login page was blank.
|
||||
|
||||
## Password policy
|
||||
### Password policy
|
||||
CWE: 521
|
||||
|
||||
This website only requires that the users passwords have 5 character and 1 number. This does not at all meet the requirements for a secure password, and means the passwords can be easily cracked.
|
||||
This website only requires that the users passwords have 5 character and 1 number. This does not at all meet the requirements for a secure password, and means the passwords can be easily cracked. It is also likely that many of the passwords will be simply 5 letters then a number. This makes it very easy to crack these passwords using a pattern technique.
|
||||
|
||||
## Use of a Broken or Risky Cryptographic Algorithm
|
||||
### Use of a Broken or Risky Cryptographic Algorithm
|
||||
CWE: 327
|
||||
|
||||
The website uses md5 to hash the passwords which is not a secure hash function. It also does not salt or pepper the passwords.
|
||||
|
||||
## Improper Restriction of Excessive Authentication Attempts
|
||||
I was able to crack 48 of the 100 passwords using hashcat and the rockyou wordlist with the command: hashcat.exe -m 0 -a 0 pwds.txt rockyou.txt.
|
||||
|
||||
### Improper Restriction of Excessive Authentication Attempts
|
||||
CWE: 307
|
||||
|
||||
The login page does not restrict the number of login attempts. This means it is possible for an attacker to attempt many passwords to gain access to an account.
|
||||
|
||||
## Path traversal
|
||||
### Path traversal
|
||||
CWE: 22
|
||||
- You can access the welcome page simply using the path /catalogue/welcome.jsp. This will load the welcome page with the username null. However it is unclear whether this is a security issue as curently the welcome page offers no functionality.
|
||||
- I dont think there are any path traversal flaws in this website. This is because there isn't any urls which contain queries or parameters relating to sensitive pages.
|
||||
|
||||
## Cleartext Transmission of Sensitive Information
|
||||
### Cleartext Transmission of Sensitive Information
|
||||
CWE: 319
|
||||
|
||||
When a user logs in, their username and unhashed password are transmitted in a cleartext post request to the server. This informaiton is susceptible to a man in the middle attack and other kinds of interception.
|
||||
|
||||
#### Example payload:
|
||||

|
||||
|
||||
## Conclusion
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user