55 lines
1.3 KiB
Markdown
55 lines
1.3 KiB
Markdown
# cspj application
|
|
|
|
## attacks
|
|
|
|
1. sql injection
|
|
2. xss
|
|
3. command injection
|
|
4. file inclusion attacks
|
|
5. csrf
|
|
6. directory traversal
|
|
7. insecure deserialization
|
|
8. session hijacking
|
|
9. xml external entity injection
|
|
10. sever side request forgery
|
|
11. broken authentication and session management
|
|
12. clickjacking
|
|
|
|
## backend
|
|
|
|
backend-for-frontend server
|
|
|
|
!remember to set the environment variables
|
|
!include this in the setup instructions
|
|
!should we use a .env file and let the user set the variables?
|
|
|
|
PGHOST=localhost
|
|
PGPORT=5432
|
|
PGDATABASE=asdfdb
|
|
PGUSER=asdfuser
|
|
PGPASSWORD=asdfpassword
|
|
|
|
## Server
|
|
|
|
!only listening on localhost is supported. DO NOT run this on a public ip.
|
|
|
|
- `/health`
|
|
- `/health-db`
|
|
- `/setup-demo-db`
|
|
- `/nuke-db`
|
|
- `/fetch-all-users`
|
|
|
|
### SQL Injection
|
|
|
|
Use `' OR 1=1; --`
|
|
|
|
- `/unsecure-register-sql`
|
|
- `/secure-register-sql`
|
|
- `/unsecure-login-sql`
|
|
- `/secure-login-sql`
|
|
|
|
#### 1. Parameterization of Queries
|
|
|
|
Used `pool.Query()` with a parameterized query, instead of dynamically constructing the SQL query by directly inserting the user input.
|
|
Parameterized queries separate the SQL code from the data, so user input is never directly put into the query's structure. Placeholders are used instead, and the data is passed as parameters. The DB will treat them as data, not executable code.
|