Who is affected
IBM Aspera Faspex is affected by an incorrect authorisation vulnerability that permits authenticated users to escalate their privileges by crafting specific messages that bypass access controls. The vulnerability applies to Faspex deployments where unauthorised privilege escalation poses a risk; the record does not specify which versions or deployment topologies are in scope.
How to check whether this touches you
- Inventory your environment for any running instance of IBM Aspera Faspex, including non-production and backup instances.
- Determine whether Faspex is reachable from the internet or from untrusted network segments where unauthenticated or low-privileged users could obtain access.
- Establish the running version number from the administrative interface or package metadata; consult IBM's advisory to map your version against the affected range and any available patches.
- Review access logs to identify the population of authenticated users with current or recent sessions.
What to do
- Obtain IBM's remediation guidance immediately and assess whether a patch is available for your version. If a patch exists, schedule its application within the federal remediation window.
- If no patch is available, implement network segmentation to restrict access to Faspex to authorised users and networks only; disable or isolate internet-facing endpoints if feasible.
- Review and tighten role-based access controls within Faspex to limit the blast radius of any unauthorised privilege escalation; document the current privilege model.
- Enable and retain detailed audit logging of authentication, authorisation decisions, and administrative actions within Faspex and any proxy or load-balancer in front of it.
- If you cannot patch or mitigate within the federal remediation due date, escalate to your security leadership and evaluate discontinuation of the product in accordance with CISA BOD 26-04 guidance.
If you find you were exposed
Exploitation of an authorisation bypass typically precedes public disclosure by weeks or months. Search your audit logs for authenticated sessions that performed administrative or sensitive operations outside their known role; pay particular attention to session-start times and the timeline of the advisory. Retention of logs is your primary constraint; if you cannot access logs older than 90 days, document the gap and flag it as a detection risk for future incidents.