취약점 도입 방식
Architecture and Design
Implementation
Implementation
System Configuration
Integration
Bundling
적용 가능한 플랫폼
언어
클래스: Not Language-Specific (Undetermined)
운영 체제
클래스: Not OS-Specific (Undetermined)
아키텍처
클래스: Not Architecture-Specific (Undetermined)
기술
이름: AI/ML (Undetermined)
일반적인 결과
| 범위 |
영향 |
가능성 |
Confidentiality Integrity Availability | Execute Unauthorized Code or Commands, Varies by Context | |
| Confidentiality | Read Application Data | |
| Integrity | Modify Application Data, Execute Unauthorized Code or Commands | |
| Access Control | Read Application Data, Modify Application Data, Gain Privileges or Assume Identity | |
관찰된 예시
| 참고 자료 |
설명 |
| Chain: LLM integration framework has prompt injection
(CWE-1427) that allows an attacker to force the service to retrieve
data from an arbitrary URL, essentially providing SSRF (CWE-918) and
potentially injecting content into downstream tasks. |
| ML-based email analysis product uses an
API service that allows a malicious user to inject a
direct prompt and take over the service logic, forcing
it to leak the standard hard-coded system prompts
and/or execute unwanted prompts to leak sensitive
data. |
| Chain: library for generating SQL via LLMs using RAG uses
a prompt function to present the user with visualized results,
allowing altering of the prompt using prompt injection (CWE-1427) to
run arbitrary Python code (CWE-94) instead of the intended
visualization code. |
| AI-based integration with business intel dashboard allows prompt injection through its natural language component, allowing execution of arbitrary code |
잠재적 완화 방법
Phases : Architecture and Design
Phases : Implementation
Phases : Architecture and Design
Phases : Implementation
Phases : Installation // Operation
Phases : System Configuration
탐지 방법
Dynamic Analysis with Manual Results Interpretation
Dynamic Analysis with Automated Results Interpretation
Architecture or Design Review
취약점 매핑 메모
근거 : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
댓글 : Ensure that the weakness being identified involves improper neutralization during prompt generation. A different CWE might be needed if the core concern is related to inadvertent insertion of sensitive information, generating prompts from third-party sources that should not have been trusted (as may occur with indirect prompt injection), or jailbreaking, then the root cause might be a different weakness.
참고 자료
REF-1450
OWASP Top 10 for Large Language Model Applications - LLM01
OWASP.
https://genai.owasp.org/llmrisk/llm01-prompt-injection/ REF-1451
IBM - What is a prompt injection attack?
Matthew Kosinski, Amber Forrest.
https://www.ibm.com/think/topics/prompt-injection REF-1452
Not what you've signed up for: Compromising Real-World LLM-Integrated Applications with Indirect Prompt Injection
Kai Greshake, Sahar Abdelnabi, Shailesh Mishra, Christoph Endres, Thorsten Holz, Mario Fritz.
https://arxiv.org/abs/2302.12173
제출
| 이름 |
조직 |
날짜 |
출시일 |
Version |
| Max Rattray |
Praetorian |
2024-06-21 +00:00 |
2024-11-19 +00:00 |
4.16 |
수정 사항
| 이름 |
조직 |
날짜 |
댓글 |
| CWE Content Team |
MITRE |
2025-09-09 +00:00 |
updated References |
| CWE Content Team |
MITRE |
2025-12-11 +00:00 |
updated Observed_Examples, Weakness_Ordinalities |
| CWE Content Team |
MITRE |
2026-04-30 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2026-10-28 +00:00 |
updated Demonstrative_Examples |