dbcve.org
Aspera SharesApplication · Ibm

CVE-2024-56470

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-05
Fix available
A fix is available. Upgrade to 1.10.0 or later.
See remediation →
60/100
Remediation priority · Elevated
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 Shares 1.9.0 through 1.10.0 PL6 is vulnerable to server-side request forgery (SSRF). This may allow an authenticated attacker to send unauthorized requests from the system, potentially leading to network enumeration or facilitating other attacks.

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 · moderate confidence

IBM Aspera Shares versions 1.9.0 through 1.10.0 PL6 contains a server-side request forgery (SSRF) vulnerability. An authenticated attacker can manipulate the application to send arbitrary HTTP requests from the server, potentially accessing internal services, cloud metadata endpoints, or performing network reconnaissance.

MitigationApply vendor patches as they become available. Until a patch is released, restrict application user permissions to the minimum required, implement URL allowlisting for permitted request destinations, and network-segment the application server to limit the impact of potential SSRF exploitation.

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 SharesApplication
Affected:>= 1.9.0, < 1.10.0= 1.10.0

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 checks

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

  1. Identify installed IBM Aspera Shares version
    Locate the version information in the application administrative interface or check the product release documentation. Common locations include the About page in the admin console or the installation directory containing version manifest files.
    Affected if The installed version is 1.9.0 through 1.10.0 PL6, or exactly 1.10.0 (any patch level).
  2. Determine if HTTP request features are accessible
    Review the application for features that allow users to configure external HTTP endpoints, webhooks, URL callbacks, or integration with external services that initiate outbound HTTP connections from the server.
    Affected if Any feature allowing users to specify or influence external URLs is enabled and accessible to authenticated users.
  3. Audit user authentication and permission assignments
    Examine which user accounts have authentication access to the Aspera Shares application and review the permission model to identify what level of access standard authenticated users possess.
    Affected if Authenticated users (beyond only administrators) can access the application and trigger the vulnerable HTTP request functionality.

A user is affected if their IBM Aspera Shares installation runs version 1.9.0 through 1.10.0 PL6 or exactly 1.10.0, and the application allows authenticated non-administrator users to access features that trigger outbound HTTP requests from the server.

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 1.10.0 or later
Fixed in 1.10.0
Interim mitigation

Apply vendor patches as they become available. Until a patch is released, restrict application user permissions to the minimum required, implement URL allowlisting for permitted request destinations, and network-segment the application server to limit the impact of potential SSRF exploitation.

Recommended fix Moderate confidence

Latest available version of Aspera Shares (check IBM for specific version containing the fix)

  1. 1. Back up the current Aspera Shares installation and configuration data.
  2. 2. Review IBM's official security bulletin for Aspera Shares for specific patch or version details.
  3. 3. Download the latest Aspera Shares version from IBM's official Aspera website or IBM Fix Central.
  4. 4. Stop the Aspera Shares service before applying the update.
  5. 5. Apply the upgrade following IBM's documented upgrade procedure for Aspera Shares.
  6. 6. Verify the upgrade was successful by checking the version number in the admin interface.
  7. 7. Restart the Aspera Shares service.
  8. 8. Test that the SSRF vulnerability is no longer present by verifying the fix.
Caveat Review IBM's release notes for any configuration or compatibility changes between versions

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

Fix this in Aspera Shares Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-56470 — 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-2024-56470 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