- Attack vector (AV:N)
- Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
- Attack complexity (AC:L)
- Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
- Privileges required (PR:N)
- No account or special rights needed—anonymous or random user is enough.
- User interaction (UI:N)
- Nobody has to click “OK” or open a trap file; it can work without a victim helping.
- Scope (S:U)
- Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
- Confidentiality (C:N)
- Doesn’t really leak secrets in a meaningful way.
- Integrity (I:N)
- Data isn’t meaningfully altered or forged.
- Availability (A:H)
- Could take the service down hard or make it unusable for people who depend on it.
- Exploit maturity (E:P)
- There’s at least a proof-of-concept or demo code out there.
- Fix status (RL:O)
- Vendor shipped an official fix you’re meant to install.
- Report confidence (RC:C)
- Treat it as confirmed—the vulnerability and impact line up with evidence.