Realized that there's a huge gap in knowledge for some taxonomy and terms in #infosec. Here's a š§µ
Let's start with CWE from @CweCapec. Common Weakness Enumeration.
* This is š« a scoring system
* This is identifier for a type of vuln
For example: SQL Injection is CWE 89
It has broad "parent" and more specific "child" categories. But EOD, they are Vulnerability IDs 2/
@CweCapec Let's look the one its most confused with. CVE (@CVEnew). This is a number that is assigned to a specific vulnerability identified against software/hardware that is publicly available (commerical/OSS). Ex: CVE-2022-0847 is a CVE given to the Linux #DirtyPipe vul. 3/
@CweCapec@CVEnew Its a specific vulnerability dataset, but it can be identified by a generic type of vulnerability i.e. CWE. In this case, the type of vulnerability is probably closer to a Buffer Overflow, i.e. CWE 119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) 4/
@CweCapec@CVEnew Then there's the scoring system CVSS (Common Vulnerability Scoring System). It consists of multiple "factors" of scoring a vulnerability based on a Base - think of it as a baseline score for a vulnerability of its nature. 5/
@CweCapec@CVEnew This is defined by params like AuthN, Access Control, C,I,A metrics and so on. Like a baseline. Then it has the "temporal" metrics, like exploitability and remediation. Things that tend to change over the lifetime of the vulnerability. finally, you have the "environmental" 6/
@CweCapec@CVEnew This refers to the specifics of the environment where the target system is deployed, that has an impact on the score of the vulnerability. Things like internal/external, collateral damage potential, etc. 7/
@CweCapec@CVEnew Finally you have CAPEC (Common Attack Pattern Enumeration and Classification). As the name suggests, these are a compendium of typical attack patterns and techniques against specific CWEs. 8/
@CweCapec@CVEnew It has multiple approaches to classification and is very complementary to....you guessed it the @MITREAttack framework. Its a thoroughly awesome and underrated taxonomy and classification set
ICYMI, this is how the #log4j#Log4Shell flaw works (in simple english), a š§µ 1. Victim is running a Java Web that uses the log4j logging lib 2. The victim web app has code that logs http request payloads/headers with log statements (example User-Agent)
1/
3. Attacker identifies vulnerable app and makes a request to the server with the User-Agent Value set to this. What does this mean? 2/
jndi == Java Naming and Directory Interface. Allows Java apps to access multiple apis for LDAP, Remote Method Invocation (RMI), etc through the JNDI Interface 4. The attacker tries to get the log4j library to lookup an LDAP server through JNDI 3/