CVE-2024-45096
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 · uneditedIBM Aspera Faspex 5.0.0 through 5.0.9 could allow a user with access to the package to obtain sensitive information through a directory listing.
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 confidenceIBM Aspera Faspex versions 5.0.0 through 5.0.9 contains a directory listing vulnerability that allows authenticated users with package access to enumerate and access sensitive files outside the intended package scope, leading to information disclosure.
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>= 5.0.0, < 5.0.10CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm IBM Aspera Faspex is installedLocate the Faspex installation directory or check system services for 'aspera' or 'faspex' processesAffected if The product is present on the system
-
Identify installed Faspex versionAccess the Faspex web interface and view the version in the About/Help section, or check version files in the installation directoryAffected if Version is 5.0.0 through 5.0.9 (versions prior to 5.0.10)
-
Verify authentication is enabledCheck Faspex authentication settings to confirm user authentication is required for accessAffected if Authentication is configured and users can log in
-
Check for existing packagesReview Faspex packages or transfers configured in the system to determine if any packages existAffected if Any packages are created or users have package access privileges
User is affected if IBM Aspera Faspex version 5.0.0-5.0.10 is installed with authentication enabled and packages are accessible to users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.0.10
Upgrade IBM Aspera Faspex to version 5.0.10 or later, or apply vendor-supplied patch to resolve the directory listing exposure.
Aspera Faspex 5.0.10
- Verify current installed version of Aspera Faspex using the administrative console or command line interface
- Review IBM Aspera Faspex 5.0.10 release notes for any migration requirements or known issues
- Create a full backup of the current Faspex installation including database and configuration files
- Download Aspera Faspex version 5.0.10 from IBM/Aspera official distribution channels
- Stop the Aspera Faspex services before upgrading
- Install Aspera Faspex 5.0.10 following the standard upgrade procedure documented in IBM installation guides
- Verify the upgrade was successful by checking the version in the administrative console
- Start Aspera Faspex services and confirm normal operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45096 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-45096 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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