Cyber Resilience

CVE-2025-13212

Ibm Aspera Console 3.3.0 – 3.4.9

Published
16 March 2026
Modified
17 March 2026
Patch / advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS Score 0.0027 19th percentile
Risk Priority 43 floored blend · peak EPSS

Summary

CVE-2025-13212 is a medium-severity Improper Control of Interaction Frequency (CWE-799) vulnerability in Ibm Aspera Console. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Brute Force (T1110); ranked at the 19th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-10 (Concurrent Session Control) and AC-7 (Unsuccessful Logon Attempts) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

IBM Aspera Console 3.3.0 through 3.4.8 could allow an authenticated user to cause a denial of service in the email service due to improper control of interaction frequency.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
T1499.002 Service Exhaustion Flood Impact
Adversaries may target the different network services provided by systems to conduct a denial of service (DoS).
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
T1667 Email Bombing Impact
Adversaries may flood targeted email addresses with an overwhelming volume of messages.
T1110.001 Password Guessing Credential Access
Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts.
T1110.003 Password Spraying Credential Access
Adversaries may use a single or small list of commonly used passwords against many different accounts to attempt to acquire valid account credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-13460Same product: Ibm Aspera Console
CVE-2023-27272Same product: Ibm Aspera Console
CVE-2025-13211Same product: Linux Linux Kernel
CVE-2025-13459Same product: Ibm Aspera Console
CVE-2025-36171Same product: Linux Linux Kernel
CVE-2024-54170Same product: Linux Linux Kernel
CVE-2024-41766Same product: Linux Linux Kernel
CVE-2025-3221Same product: Linux Linux Kernel
CVE-2025-0158Same product: Linux Linux Kernel
CVE-2025-36225Same product: Linux Linux Kernel

Affected Assets

ibm
aspera console
3.3.0 — 3.4.9

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

ac-10 enforces a hard limit on concurrent sessions per user, directly stopping uncontrolled interaction frequency at the session level.

ac-7 directly enforces a limit on the frequency of invalid authentication attempts, structurally preventing the weakness for that interaction class.

sc-5 reduces the impact of excessive request volume (DoS) but does not itself impose the frequency controls whose absence defines the weakness.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.IR-01 partial match
prevents

Protecting networks from unauthorized usage can incorporate rate limiting to bound interaction frequency.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

mitigates

Network security controls can enforce rate limiting and throttling at the perimeter.

prevents

Application security requirements explicitly include controls on interaction frequency and throttling.

prevents

Secure architecture principles recommend rate-limiting and resource-management mechanisms.

prevents

Secure coding practices can embed input-frequency and throttling checks in code.

degrades

Capacity management directly limits request rates and resource exhaustion that CWE-799 describes.

References