Cyber Resilience

CVE-2024-45097

Ibm Aspera Faspex 5.0.0 – 5.0.10

Published
05 September 2024
Modified
06 September 2024
Patch / advisory
View advisory
CVSS Score v3.1 5.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:N
EPSS Score 0.0031 23th percentile
Risk Priority 45 floored blend · peak EPSS

Summary

CVE-2024-45097 is a medium-severity Trusting HTTP Permission Methods on the Server Side (CWE-650) vulnerability in Ibm Aspera Faspex. Its CVSS base score is 5.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 23th 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-3 (Access Enforcement) and SA-11 (Developer Testing and Evaluation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A06:2025 Insecure Design

EU & UK References

Vulnerability Data

IBM Aspera Faspex 5.0.0 through 5.0.9 could allow a user to bypass intended access restrictions and conduct resource modification.

CWE(s)
CWE-650CWE-436

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-45098Same product: Ibm Aspera Faspex
CVE-2025-36039Same product: Ibm Aspera Faspex
CVE-2023-37412Same product: Ibm Aspera Faspex
CVE-2023-37411Same product: Ibm Aspera Faspex
CVE-2025-36230Same product: Ibm Aspera Faspex
CVE-2025-36040Same product: Ibm Aspera Faspex
CVE-2024-45096Same product: Ibm Aspera Faspex
CVE-2023-35907Same product: Ibm Aspera Faspex
CVE-2023-27279Same product: Ibm Aspera Faspex
CVE-2023-37400Same product: Ibm Aspera Faspex

Affected Assets

ibm
aspera faspex
5.0.0 — 5.0.10

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V3.5.1
  • V3.5.3
  • V4.1.4

Mitigating Controls (NIST 800-53 r5) AI

AC-3 Access Enforcement good match

AC-3 enforces authorizations for resource access without permitting unsafe assumptions about request methods to bypass checks.

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover cases where two products interpret the same inputs or state transitions differently.

SI-10 Information Input Validation good match

Strict, consistently applied input validation reduces the chance that one product will accept data the other product rejects or interprets differently.

SA-8 Security and Privacy Engineering Principles partial match

Applying security engineering principles during design can require unambiguous protocol and data-format specifications that eliminate divergent interpretations between products.

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.PS-06 mostly match
prevents

Secure SDLC practices directly prevent flawed assumptions about HTTP method safety during design and coding.

DE.AE-03 partial match
prevents

Correlating logs from multiple products can surface discrepancies caused by interpretation conflicts.

DE.CM-09 partial match
prevents

Runtime monitoring of software behavior can detect adverse outcomes stemming from differing interpretations.

GV.SC-07 partial match
prevents

Supplier risk assessments can identify products whose differing interpretations create systemic exposure.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover this server-side logic flaw through testing or scanning.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect and prevent vulnerabilities where GET requests cause unintended state changes.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle can require consistent interface contracts and canonicalization rules that reduce interpretation conflicts between components.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate proper HTTP method usage and state-changing operation restrictions.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture principles include proper HTTP method handling and RESTful design to prevent state changes via GET.

A.8.28 Secure coding partial match
prevents

Secure coding practices directly address improper HTTP method usage and ensure state-changing operations use POST/PUT/DELETE.

References