CVE-2025-13460
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 Console 3.3.0 through 3.4.8 could allow an attacker to enumerate usernames due to an observable response discrepancy.
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 Console versions 3.3.0 through 3.4.8 contains a username enumeration vulnerability where the application returns different responses for valid versus invalid usernames during authentication, allowing attackers to discover valid user accounts through systematic probing.
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>= 3.3.0, < 3.4.9CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Identify installed IBM Aspera Console versionLocate the Aspera Console version through its web interface admin panel, installation directory metadata, or product release documentation. Common locations include the About section in the console UI or version files in the installation directory.Affected if Installed version is 3.3.0 through 3.4.8 (versions below 3.4.9 are affected)
-
Confirm authentication endpoint is accessibleVerify that the Aspera Console login page or authentication API endpoint is reachable over the network. This is typically found at the console's web URL path for authentication.Affected if The login interface is externally or internally accessible without additional access controls
-
Test authentication response for invalid usernameSubmit a login request using a clearly invalid/non-existent username (e.g., 'nonexistentuser123') to the authentication endpoint and capture the HTTP response status and message.Affected if Response indicates the username does not exist or provides specific feedback about username validity
-
Test authentication response for valid usernameSubmit a login request using a known-valid username (or test with several usernames) with an incorrect password, then capture the response.Affected if Response differs from the invalid username case (e.g., returns a different error message, different HTTP status code, or mentions password rather than username)
Environment is affected if IBM Aspera Console version is 3.3.0 through 3.4.8 AND the authentication endpoint returns measurably different responses for valid versus invalid usernames.
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 · scoped3.4.9
Implement uniform error responses for all authentication failures to prevent username enumeration, ensuring the application returns the same message regardless of whether the username exists.
3.4.9
- Verify the current installed version of IBM Aspera Console by accessing the console's admin interface or checking the installation
- Review the IBM Aspera Console 3.4.9 release notes and upgrade documentation for any prerequisites
- Create a full backup of the current Aspera Console installation and database
- Schedule a maintenance window for the upgrade
- Follow IBM's standard upgrade procedure for Aspera Console, typically involving stopping the service, applying the new version, and restarting
- Verify the upgrade was successful by checking the console version and ensuring all services are running
- Test that user authentication works correctly to confirm the username enumeration vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13460 — 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-2025-13460 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