dbcve.org
Aspera FaspexApplication · Ibm

CVE-2025-33137

HIGH · 8.8 CVSS v3.1 Published 2025-05-22
Fix available
A fix is available. Upgrade to 5.0.12.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
IBM Aspera Faspex 5.0.0 through 5.0.12 could allow an authenticated user to obtain sensitive information or perform unauthorized actions on behalf of another user due to client-side enforcement of server-side security.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

IBM Aspera Faspex versions 5.0.0-5.0.12 relies on client-side enforcement (e.g., hidden fields, dropdown values, or API parameters) for server-side security decisions instead of proper server-side authorization validation. This allows any authenticated user to access sensitive information or perform unauthorized actions on behalf of other users by manipulating client-supplied data.

MitigationUpgrade to IBM Aspera Faspex version 5.0.13 or later which implements proper server-side authorization validation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Aspera FaspexApplication
Affected:>= 5.0.0, < 5.0.12.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed IBM Aspera Faspex version
    Locate the Faspex version information through the application admin interface (typically under Help > About or System > Version), or check version files in the installation directory if you have server access.
    Affected if The detected version falls within 5.0.0 through 5.0.12.1 (i.e., version is greater than or equal to 5.0.0 but less than 5.0.12.1).
  2. Confirm Faspex web interface is accessible
    Verify that the Faspex web interface is reachable and operational. The vulnerability applies to authenticated users accessing the web application.
    Affected if The Faspex web interface is exposed and users can authenticate to the system.
  3. Review client-side data handling in API responses
    Inspect network traffic or API responses when logged in as a standard user. Look for sensitive data references (such as user IDs, file IDs, or other object identifiers) passed in visible fields like dropdown values, hidden form fields, or API parameters that could be manipulated.
    Affected if Sensitive identifiers or data are exposed in client-accessible fields that could be modified by an authenticated user to access other users' data.

Your environment is affected if the installed IBM Aspera Faspex version is 5.0.0 or higher but lower than 5.0.12.1, and the web interface is accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.0.12.1 or later
Fixed in 5.0.12.1
Interim mitigation

Upgrade to IBM Aspera Faspex version 5.0.13 or later which implements proper server-side authorization validation.

Recommended fix High confidence

5.0.12.1

  1. 1. Review IBM Aspera Faspex 5.0.12.1 release notes for any upgrade prerequisites or注意事项
  2. 2. Create a full backup of the current Faspex database and configuration files
  3. 3. Schedule a maintenance window as the upgrade will require service interruption
  4. 4. Download the Aspera Faspex 5.0.12.1 package from IBM/Aspera
  5. 5. Stop the Faspex services (asperahttpd, asperafasp, asperafcpx)
  6. 6. Run the upgrade installer following IBM's standard upgrade procedures
  7. 7. Verify the upgrade completed successfully by checking the version number in the Faspex admin interface
  8. 8. Test that authentication and user authorization work correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Aspera Faspex Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-33137 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-33137 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data