Skip to main content
LLM Security Database
Skip to research details
Back to research findings
LMVD-ID: f2ab1b94
Paper published December 1, 2024
Entry analyzed February 2, 2025
Paper-reported evidence
Confidence: Source-linked

The LMVD-ID is an internal research identifier, not an official CVE identifier.

Targeted Bit-Flip Jailbreak

A vulnerability exists in large language models (LLMs) where targeted bitwise corruptions in model parameters can induce a "jailbroken" state, causing the model to generate harmful responses without input modification…

BibTeX citation

Paper-evaluated models(7)

Llama 2 13B, Llama 2 7B, Llama 3 8B +4 more
  • Llama 2 13B
  • Llama 2 7B
  • Llama 3 8B
  • Qwen 2 1.5B
  • Qwen 2 7B
  • Vicuna 13B
  • Vicuna 7B

Description

A vulnerability exists in large language models (LLMs) where targeted bitwise corruptions in model parameters can induce a "jailbroken" state, causing the model to generate harmful responses without input modification. Fewer than 25 bit-flips are sufficient to achieve this in many cases. The vulnerability stems from the susceptibility of the model's memory representation to fault injection attacks.

Examples

Specific examples demonstrating the attack are detailed within the research paper "PrisonBreak: Jailbreaking Large Language Models with Fewer Than Twenty-Five Targeted Bit-flips". See arXiv:2412.07192 (opens in a new tab).

Impact

Successful exploitation allows an attacker to permanently circumvent safety mechanisms implemented in LLMs, enabling the generation of arbitrary harmful content. This poses a significant risk to the security and reliability of LLM-powered applications and services. The attack requires minimal parameter modification, making it potentially difficult to detect.

Affected Systems

Large language models (LLMs) deployed in memory using half-precision (16-bit) floating-point representations, particularly those trained with safety mechanisms such as supervised fine-tuning (SFT), reinforcement learning with human feedback (RLHF), and direct preference optimization (DPO). Systems utilizing vulnerable DRAM susceptible to Rowhammer attacks are also affected.

Mitigation Steps

  • Implement robust fault-tolerance mechanisms capable of detecting and correcting bit-flips in model parameters.
  • Utilize memory protection techniques to mitigate Rowhammer attacks.
  • Employ model-level defenses that limit the impact of bitwise corruptions, such as parameter quantization with robust reconstruction or activation clamping within safe bounds. However, careful consideration needs to be given to the possible circumvention via adaptive attacks.
  • Regularly audit and update LLMs to patch vulnerabilities and improve resilience to attacks. This includes the rigorous testing of safety mechanisms against various types of attacks, and the development of robust model monitoring systems.

Research context and confidence

Evidence and verification
Paper-reported; independent reproduction is not documented.
Primary research source linked.
Severity
Not rated by this catalog.
Source and publication type
arXiv · Research preprint.
Peer-review status is not provided by this source.
Author and publication status
Author metadata is not stored; see the primary paper.
Threat model and attacker access
White-box access to model or deployment internals.
Related deployment categories
No related deployment category is classified.
Taxonomy labels only; paper-specific deployment prerequisites are not inferred.
Affected systems
Large language models (LLMs) deployed in memory using half-precision (16-bit) floating-point representations, particularly those trained with safety mechanisms such as supervised fine-tuning (SFT), reinforcement…

Research Paper

PrisonBreak: Jailbreaking Large Language Models with Fewer Than Twenty-Five Targeted Bit-flips

Primary source: arXiv. Findings are reported by the cited research and have not been independently verified.

View Paper

Evidence

This entry is based on a primary research source. Its findings are paper-reported; independent reproduction and verification are not claimed.

https://arxiv.org/abs/2412.07192