---
title: "CAPEC-489: SSL Flood"
url: https://radicalnotion.ai/capec/capec-489
type: capec
description: "An adversary may execute a flooding attack using the SSL protocol with the intent to deny legitimate users access to a service by consuming all the available resources on the server side. These attacks take advantage of the asymmetric relationship between the processing power used by the client and the processing power used by the server to create a secure connection. In this manner the attacker can make a large number of HTTPS requests on a low provisioned machine to tie up a disproportionately large number of resources on the server. The clients then continue to keep renegotiating the SSL connection. When multiplied by a large number of attacking machines, this attack can result in a crash or loss of service to legitimate users."
updated: 2026-06-01
source: RadicalNotion.AI
license: CC BY-NC 4.0 (https://creativecommons.org/licenses/by-nc/4.0/)
---

# CAPEC-489: SSL Flood

- **Abstraction:** Standard
- **Status:** Draft
- **CAPEC catalog version:** 3.9

## Description

An adversary may execute a flooding attack using the SSL protocol with the intent to deny legitimate users access to a service by consuming all the available resources on the server side. These attacks take advantage of the asymmetric relationship between the processing power used by the client and the processing power used by the server to create a secure connection. In this manner the attacker can make a large number of HTTPS requests on a low provisioned machine to tie up a disproportionately large number of resources on the server. The clients then continue to keep renegotiating the SSL connection. When multiplied by a large number of attacking machines, this attack can result in a crash or loss of service to legitimate users.

## Prerequisites

- This type of an attack requires the ability to generate a large amount of SSL traffic to send a target server.

## Mitigations

- To mitigate this type of an attack, an organization can create rule based filters to silently drop connections if too many are attempted in a certain time period.

## Related weaknesses (CWE)

- [CWE-770](https://radicalnotion.ai/cwe/cwe-770): Allocation of Resources Without Limits or Throttling

## Related attack patterns

| Relationship | CAPEC | Name |
| --- | --- | --- |
| Parent | [CAPEC-125](https://radicalnotion.ai/capec/capec-125) | Flooding |

## Taxonomy mappings

| Taxonomy | Entry | Id |
| --- | --- | --- |
| ATTACK | Endpoint Denial of Service:Service Exhaustion Flood | 1499.002 |

## Frequently asked questions

### What is CAPEC-489?

An adversary may execute a flooding attack using the SSL protocol with the intent to deny legitimate users access to a service by consuming all the available resources on the server side. These attacks take advantage of the asymmetric relationship between the processing power used by the client and the processing power used by the server to create a secure connection. In this manner the attacker can make a large number of HTTPS requests on a low provisioned machine to tie up a disproportionately large number of resources on the server. The clients then continue to keep renegotiating the SSL connection. When multiplied by a large number of attacking machines, this attack can result in a crash or loss of service to legitimate users.

### How do you prevent CAPEC-489?

To mitigate this type of an attack, an organization can create rule based filters to silently drop connections if too many are attempted in a certain time period.

### What weaknesses does CAPEC-489 target?

CAPEC-489 exploits one CWE weakness: CWE-770 (Allocation of Resources Without Limits or Throttling).

Primary source: [MITRE CAPEC](https://capec.mitre.org/data/definitions/489.html)

---

Source: [RadicalNotion.AI](https://radicalnotion.ai/capec/capec-489). Licensed CC BY-NC 4.0; attribute RadicalNotion.AI and link the source page when you reuse this data.
