- Attack vector (AV:L)
- They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
- 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:H)
- They need powerful rights—admin, root, or similar—before this pays off.
- 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:H)
- They could widely tamper with or forge data—trust in the data is badly hurt.
- Availability (A:N)
- Service keeps running; no real outage angle.