I introduce what I think is a new idea to track and relate vulns to each other in a data store.
In AppSec, most people understand that context is everything when it comes to assigning risk. Certain factors and other vulnerabilities, when combined together, can increase the severity of a vulnerability. Defenders and bug hunters alike help organizations understand a more accurate threat landscape from experience, but it's not something that is well documented. Join Curtis as he discuses this gap and introduces some tools and new resources for vuln chaining.
%in Midrand+277-882-255-28 abortion pills for sale in midrand
Â
Using Vuln Chaining and Other Factors for a Better Risk Perspective
1. Using Vuln Chaining and Other
Factors for a Better Risk
Perspective
By Curtis Brazzell (Say Hi @curtbraz on Twitter/LinkedIn/Gmail!)
2. About Me?
ď‚š Interested in computers/security from an early age
ď‚š Former DBA/Sys Admin (4-6 years)
ď‚š Security field for 10+ years (mostly consulting)
ď‚š Sr SOC Analyst
ď‚š DFIR Lead (Malware Analysis)
ď‚š AppSec/Pentesting/Red Team
ď‚š Currently an MSC for GuidePoint Security on the AppSec (Tactical) Team
ď‚š Passionate about anything security (especially phishing!)
 Want to be known for research/tool contributions (known instead for …. )
ď‚š Like to try to put a new spin on old topics
3. Severity Ratings
ď‚š Importance for accuracy to understand risk
ď‚š Can be subjective
ď‚š Should be challenged!
ď‚š Context is everything!
ď‚š Unique environments
ď‚š External/Internal
ď‚š Pre-Auth/Auth
ď‚š Roles/Permissions/Privileges
ď‚š Exploitability
ď‚š Compensating controls / mitigations
ď‚š CVSS/CWSS
4. Severity Ratings
ď‚š Common Vulnerability Scoring System (CVSS)
ď‚š Open Framework
ď‚š Three metric groups:
ď‚š Base (What you get by default from most vuln scanners using the NVD)
ď‚š Temporal (Metrics that change over time due to external events)
ď‚š Environmental (Impact of the vuln on your org)
CVSS v3.0 Ratings
Severity Base Score Range
None 0.0
Low 0.1-3.9
Medium 4.0-6.9
High 7.0-8.9
Critical 9.0-10.0
5. Severity Ratings
ď‚š Common Weakness Scoring System (CWSS)
ď‚š Can be used in conjunction with the Common Weakness Risk Analysis Framework (CWRAF)
ď‚š Three metric groups:
ď‚š Base (Inherent risk, confidence, and strength on controls)
ď‚š Attack Surface (Barriers an attacker must overcome to exploit)
ď‚š Environmental (Characteristics that are specific to an environment/context)
ď‚š Ranges between 0 and 100
6. Getting it Wrong
ď‚š Getting Impact, likelihood of attack, or exploitability wrong (also subjective)
ď‚š Missing vulnerabilities or not taking the vuln far enough
ď‚š Lack of experience (bug bounties, new hires, etc)
ď‚š Lack of time
ď‚š Misunderstanding of the environment
ď‚š Industry
ď‚š What the app does
ď‚š Ask for demos!
ď‚š May be a non-issue even
ď‚š Dangers of getting it wrong
 Too low and it doesn’t get prioritized / risk isn’t acknowledged
 Too high and you take priority from more important issues / dev time / other resources / client or app’s reputation
7. Vuln Chaining 101
ď‚š Combining vulnerabilities for a greater impact!
ď‚š More than one lower-serverity issue may be combined for a higher risk rating
 Vulns don’t live in a vacuum!
ď‚š Examples:
8. Vuln Chaining (Examples)
Cross-Site Scripting (XSS) Unprotected Session Cookie
Medium Low
High
OR Local Storage Session
Low
Session Hijacking/Account Takeover
Credit to blog.ropnop.com/storing-tokens-in-browser
9. Vuln Chaining (Examples)
Cross-Site Scripting (XSS) CORS/CSP Misconfiguration Sensitive Data Leakage / 3P Scripts (Beef)
Medium High
Medium
XSS Payload = <script src=“thirdpartydomain/hook.js”>
10. Vuln Chaining (Examples)
Header Injection Duplicate Headers / Newline Chars Cross-Site Scripting / Host Poisoning, etc
High
Medium
High
Adding newline characters to break into the body or cut off / duplicate headers
13. Vuln Chaining (Examples)
Unrestricted File Uploads Authorization Issues (No Auth) XSS/Form Jacking/Open Redirects
Medium Low High
With Auth SSRF/RCE/XXE
High
OR
& IDOR
14. Vuln Chaining
 Where’s the documentation?
ď‚š If I come across a vuln, how do I know what others to look for?
 Experienced people “just know” from memory
ď‚š Individual ones (like the previous examples) are often on blogs and public bug bounty reports
ď‚š My Idea / Contribution / Project..
ď‚š Create a community-driven open resource!
ď‚š Why am I doing this?
18. Vuln Chaining (Practical Uses)
ď‚š Used by an AppSec resource for more accurate assessments
ď‚š Educational Resource / Training | Better Bug Bounties
ď‚š Used by an internal org for threat modeling self-assessments
ď‚š Examples of use:
20. Other Uses and Closing Thoughts
ď‚š Could be implemented as a tool to import a CSV template (think compliance)
ď‚š Would love to see integration into vuln scanners by default
ď‚š Burp Extender plugin FTW! (Any takers?)
ď‚š Cool card game? (Think Backdoors & Breaches or the OWASP deck)
21. Thank You! Questions?
 We’re hiring AppSec folks at GuidePoint Security!
ď‚š Tactical and Strategic Services