Automatically detecting security vulnerabilities in WordPress
•Download as PPTX, PDF•
0 likes•627 views
Steve Hulet presentation slides on automatically detecting security vulnerabilities in WordPress.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Automatically detecting security vulnerabilities in WordPress
Similar to Automatically detecting security vulnerabilities in WordPress (20)
Recently uploaded
Recently uploaded (20)
Automatically detecting security vulnerabilities in WordPress
- 1. Automatically detecting security vulnerabilities in WordPress
- 2. Some common vulnerabilities ● SQL Injection ● Cross-Site Request Forgery (CSRF) ● Cross-Site Scripting (XSS) ● Using Components with Known Vulnerabilities
- 3. All on the Open Web Application Security Project (OWASP) "Top 10" Most Critical Web Application Security Risks 2017
- 4. SQL Injection "Injection flaws, such as SQL, OS, XXE, and LDAP injection occur when untrusted data is sent to an interpreter as part of a command or query. The attacker’s hostile data can trick the interpreter into executing unintended commands or accessing data without proper authorization." - OWASP Top 10 Application Security Risks – 2017
- 7. Cross-Site Request Forgery (CSRF) "A CSRF attack forces a logged-on victim’s browser to send a forged HTTP request, including the victim’s session cookie and any other automatically included authentication information, to a vulnerable web application. Such an attack allows the attacker to force a victim’s browser to generate requests the vulnerable application thinks are legitimate requests from the victim." - OWASP Top 10 Application Security Risks – 2017
- 10. Cross-Site Scripting (XSS) "XSS flaws occur whenever an application includes untrusted data in a new web page without proper validation or escaping, or updates an existing web page with user supplied data using a browser API that can create JavaScript. XSS allows attackers to execute scripts in the victim’s browser which can hijack user sessions, deface web sites, or redirect the user to malicious sites." - OWASP Top 10 Application Security Risks – 2017
- 15. ● mkdir -p /tmp/demo && cd /tmp/demo ● wp core download ● wp core config ● wp core install ● wp plugin install akismet --force --version=3.1 ● cat ~/phpcs-sql.xml ● phpcs -p --standard=~/phpcs-sql.xml wp-content/plugins/akismet ● cat ~/phpcs-csrf.xml Demo
- 17. Using Components with Known Vulnerabilities "Components, such as libraries, frameworks, and other software modules, run with the same privileges as the application. If a vulnerable component is exploited, such an attack can facilitate serious data loss or server takeover. Applications and APIs using components with known vulnerabilities may undermine application defenses and enable various attacks and impacts." - OWASP Top 10 Application Security Risks – 2017
- 19. Demo ● wp vuln status ● There is no step 2
- 20. Questions
- 21. Thank you!
Editor's Notes
- Next: So, how do we prevent this type of attack?
- Next: So, how do we prevent this type of attack?
- Next: So, how do we prevent this type of attack?
- Memory is fallible https://github.com/squizlabs/PHP_CodeSniffer
- Checks exist https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards
- --- if using Docker: set up alias for wp() https://github.com/wp-cli/wp-cli/issues/1838#issuecomment-254307862 /etc/init.d/mysql start ... (install plugins) (add phpcs .xml files for demo) ---
- PHPCS ruleset XML
- WP CLI extension https://github.com/10up/wp-vulnerability-scanner