CVE-2023-42526

Limiting concurrent sessions directly prevents uncontrolled resource consumption by capping the number of active sessions per user or account.

Analysis identifies uncontrolled resource consumption indicative of denial-of-service or abuse attempts.

Contingency plan testing includes resource exhaustion scenarios to verify recovery, making it harder for attackers to sustain exploits that cause uncontrolled consumption.

Updated contingency plans include current procedures to detect, contain, and recover from resource exhaustion, limiting an attacker's ability to sustain impact from uncontrolled consumption.

Alternate site allows resumption of operations if resource exhaustion at the primary site is exploited to cause unavailability.

Alternate telecommunications services enable resumption of essential functions when primary services become unavailable due to uncontrolled resource consumption.

The team can analyze and respond to resource exhaustion incidents, reducing the impact of attacks that exploit uncontrolled consumption weaknesses.

Timely maintenance support and spare parts enable rapid recovery from failures induced by uncontrolled resource consumption, shortening the impact window of denial-of-service attacks.

Pre-agreed severity-based prioritization and resource allocation during incident triage reduce the likelihood that an attacker-induced resource exhaustion will overwhelm the organization before corrective action is taken.

Early notification of anomalous resource consumption or system malfunctions enables throttling or isolation before availability is lost.

Specifying log storage limits and rotation procedures reduces the risk that unbounded log growth will exhaust disk or memory resources and cause denial of service.

Resource-utilization monitoring and alerting on bottlenecks or overloads limits the impact of denial-of-service or resource-exhaustion attacks.

A.8.20 implements network-level protections (firewalls, segmentation, protocol hardening, monitoring, authentication of systems/devices) that can limit abuse of a resource-consuming weakness but do not stop the weakness from being exploitable; the flaw remains present in the product and can still be triggered from an authorized or internal context.

Monitoring network service usage and applying controls to restrict access when necessary limits an attacker’s ability to consume excessive resources through unrestricted or unauthenticated service calls.