Authenticated resource modification via trusted HTTP permission methods
Published Sep 5, 2024 · Updated Sep 5, 2024
Authorization bypass in IBM Aspera Faspex 5.0.0 through 5.0.9 allows remote authenticated users to modify protected resources. IBM identifies server-side trust in HTTP permission methods but does not disclose the affected endpoint or exact omitted authorization check. A low-privileged account and a high-complexity network request are required; exploitation permits protected-resource access and modification without interrupting service.
Summary
What happened
Authorization bypass in IBM Aspera Faspex 5.0.0 through 5.0.9 allows remote authenticated users to modify protected resources. IBM identifies server-side trust in HTTP permission methods but does not disclose the affected endpoint or exact omitted authorization check. A low-privileged account and a high-complexity network request are required; exploitation permits protected-resource access and modification without interrupting service.
The record
- CVE
- CVE-2024-45098
- Published
- Sep 5, 2024
- Updated
- Sep 5, 2024
- Vendor
- IBM
- Product
- IBM Aspera Faspex
- Classifications
- CWE-650
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 5, 2024CVE publishedPublication date reported by the CVE source.
- Sep 5, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.0.0 <=5.0.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo