Where Do LLM-based Systems Break? A System-Level Security Framework for Risk Assessment and Treatment
Organizations: School of Informatics, Computing, and Cyber Systems, Northern Arizona University, Flagstaff, USA · Department of Software Science, Tallinn University of Technology, Tallinn, Estonia
Abstract
Large Language Models (LLMs) are increasingly integrated into safety-critical workflows, yet existing security analyses remain fragmented and often isolate model behavior from the broader system context. This work introduces a goal-driven risk assessment framework for LLM-powered systems that combines system modeling with Attack-Defense Trees (ADTrees) and Common Vulnerability Scoring System (CVSS)-based exploitability scoring to support structured, comparable analysis. We demonstrate the framework through a healthcare case study, modeling multi-step attack paths targeting intervention in medical procedures, leakage of electronic health record (EHR) data, and disruption of service availability. Our analysis indicates that threats spanning (i) conventional cyber, (ii) adversarial ML, and (iii) conversational attacks that manipulate prompts or context often consolidate into a small number of dominant paths and shared system choke points, enabling targeted defenses to yield meaningful reductions in path exploitability. By systematically comparing defense portfolios, we align these risks with established vulnerability management practices and provide a domain-agnostic workflow applicable to other LLM-enabled critical systems.
Figures & tables
| Level | Label | Engineering effort | Infra / tooling footprint | Operations load | UX / process impact |
|---|---|---|---|---|---|
| 1 | Very Low | Minor policy/config; single engineer; no core-path code changes | Reuse existing services; no new components | “Set-and-forget” checks; negligible monitoring | Invisible to users |
| 2 | Low | Small project; limited code changes; one team | Add a light service/lib; standard CI/CD integration | Periodic checks/rotations; light on-call playbooks | Minor extra step for some users |
| 3 | Medium | Cross-team work; non-trivial refactors; integration/testing | Multiple services or control plane; new secrets/PKI | Continuous upkeep (dashboards, tuning); measurable SOC workload | Noticeable friction/training; workflow changes |
| 4 | High | Org-wide program; architectural changes; specialized skills | New platform class or hardware; PKI re-plumb; broad dependency changes | Dedicated runbooks/audits; sustained operators; compliance reporting | Significant user/process change; likely perf/latency trade-offs |
| Branch | Precondition CVEs (examples) | Execution CVEs (examples) | Base (S:U) | |||
|---|---|---|---|---|---|---|
| B1: Prompt Injection | User hijacking (CVE-2025-22222); User machine hijack (CVE-2025-22457/53770/32433); Malicious user (CVE-2025-42957); Stolen API key (CVE-2024-12012); HTTPS MiTM (CVE-2024-50691) | Direct injection (CVE-2024-5184); Indirect injection (CVE-2025-46059) | 3.89 | Low | (0.00, 0.56, 0.00) | 7.5 (High) |
| B2: LLM Session Mismanagement | Weak authentication (CVE-2025-46801); Lack of session isolation (CVE-2025-32441); No context purging (CVE-2023-4969) | Session hijacking (CVE-2024-6587); Session fixation (CVE-2024-38513) | 3.89 | Low | (0.00, 0.56, 0.00) | 7.5 (High) |
| B3: Orchestration Errors | Lack of integrity checks (CVE-2025-59334); Weak orchestration API auth (CVE-2025-46801); Unvalidated shared context (CVE-2023-29374) | Task injection (CVE-2024-8156); Task mismanagement (CVE-2022-29164); Memory poisoning (CVE-2024-8309); Agent-in-the-middle (CVE-2025-6159) | 3.89 | Low | (0.00, 0.56, 0.00) | 7.5 (High) |
| B4: Model Tampering | Access to model artifacts (CVE-2023-6018); Lack of integrity verification (CVE-2025-59334) | Poisoning (CVE-2024-5185); Model replacement (CVE-2025-24357); Model extraction (CVE-2024-6868) | 3.89 | Low | (0.00, 0.56, 0.00) | 7.5 (High) |
| B5: Web MiTM | — | HTTPS MiTM (CVE-2024-50691) | 2.22 | High | (0.00, 0.56, 0.00) | 5.9 (Medium) |
| Branch | Precondition CVEs (examples) | Execution CVEs (examples) | Base (S:U) | |||
|---|---|---|---|---|---|---|
| B1: User Session Compromise | Reused from (no additional precondition family in ) | MitM on web session (CVE-2024-50691, , High) OR Prompt Injection (Direct/Indirect; CVE-2024-5184 / CVE-2025-46059, , Low) | 3.89 | – (OR reuse) | (0.56, 0.00, 0.00) | 7.5 (High) |
| B2: LLM Session Compromise | Weak authentication (CVE-2025-46801, ); Lack of session isolation (CVE-2025-32441, ); No context purging (CVE-2023-4969, ); Cross-session leakage (CVE-2024-27935, ) | Reused from : Session hijacking (CVE-2024-6587, ), Session fixation (CVE-2024-38513, ); Cache compromise: Cross-user cache exposure (CVE-2023-2885, ) OR KV-cache leakage / PromptPeek-style (CVE-2024-27935, ) | 3.89 | Low | (0.56, 0.00, 0.00) | 7.5 (High) |
| B3: Model Extraction (Training Data Leakage) | Accessible query interface (CVE-2024-32965, ); Missing rate limiting (CVE-2024-51557, ); Insufficient output filtering (CVE-2024-3402, ) | Extraction / inversion / membership inference ( no CVE ) | 3.89 | Low | (0.56, 0.00, 0.00) | 7.5 (High) |
| Branch | Precondition CVEs | Execution CVEs | Base (S:U) | |||
|---|---|---|---|---|---|---|
| B1: Prompt flooding | (shared) | CVE-2025-46569 (prompt-chaining / flooding DoS, ) | 2.84 | Low | (0.00, 0.00, 0.56) | 6.5 (Medium) |
| B2: Orchestrator abuse | (shared) | CVE-2025-48956 (infinite agent/tool loops, ) | 3.89 | Low | (0.00, 0.00, 0.56) | 7.5 (High) |
| B3: Resource exhaustion | (shared) | CVE-2025-61771 (resource exhaustion, ) | 3.89 | Low | (0.00, 0.00, 0.56) | 7.5 (High) |
| B4: External tool / API dependency | (shared) | CVE-2024-2466 (external API DoS / upstream outage trigger, ) | 3.89 | Low | (0.00, 0.00, 0.56) | 7.5 (High) |
| B5: Prompt injection (availability misuse) | (shared) | Reused from : CVE-2024-5184 (direct injection) / CVE-2025-46059 (indirect injection), | 3.89 | Low | (0.00, 0.00, 0.56) | 7.5 (High) |
| B6: Model tampering (availability impact) | (shared) | Reused from model-tampering branch (e.g., poisoning/replacement vectors), | 3.89 | Low | (0.00, 0.00, 0.56) | 7.5 (High) |
| ID | Defense Set (post-treatment; after hardening) | Final Base (S:U) | Cost | ||||
|---|---|---|---|---|---|---|---|
| Baseline | None (original path; no added controls) | 3.89 | L | 3.89 | 3.89 | 7.5 (High) | – |
| S1 | Harden one major precondition: User–Machine hijack device binding / session attestation (AC:H, PR:L) | 2.84 | L | 3.89 | 2.84 | 6.5 (Med) | 3 |
| S2 | Harden all preconditions: User Hijack: MFA + short-lived tokens (PR:H, AC:H); User–Machine: device binding (AC:H, PR:L); Malicious User: RBAC (PR:H); Stolen API Key: scope limiting (PR:H); MitM: TLS 1.3 + pinning (PR:L) | 1.62 | H | 2.22 | 1.62 | 5.3 (Med) | 2–3 |
| S3 | Harden execution only (lightweight): Canonicalization + delimited channels + sandwich-prevention rules | 3.89 | L | 2.22 | 2.22 | 5.9 (Med) | 1–3 |
| S4 | Harden both: S2 preconditions + HITL gate for high-impact actions | 1.62 | H | 1.62 | 1.62 | 5.3 (Med) | 2–4 |
| ID | Defense Set (post-treatment; after hardening) | Final Base (S:U) | Cost | ||||
|---|---|---|---|---|---|---|---|
| Baseline | None (original path; no added controls) | 3.89 | L | 3.89 | 3.89 | 7.5 (High) | – |
| S1 | Harden major preconditions only: mTLS on orchestrator APIs ; context segmentation + write-RBAC | 2.84 | L | 3.89 | 2.84 | 6.5 (Med) | 2–4 |
| S2 | Harden all preconditions: sign & verify orchestration artifacts ; mTLS on APIs ; context segmentation + write-RBAC | 1.62 | H | 2.22 | 1.62 | 5.3 (Med) | 3–4 |
| S3 | Harden execution only: task allowlisting + task/plan signing; task-sequence enforcement; context integrity checks; agent-response signing/verification | 3.89 | L | 1.62 | 1.62 | 5.3 (Med) | 2–4 |
| S4 | Harden both: S2 preconditions + S3 execution controls | 1.62 | H | 1.62 | 1.62 | 5.3 (Med) | 3–4 |