Security fixes are released in a new version of aspera-cli.
They are not back-ported to older versions.
| Version | Supported |
|---|---|
| Latest release | ✅ |
| Older releases | ❌ Upgrade to the latest release |
Supported Ruby versions are listed in the manual: Ruby.
Do not report a security vulnerability in a public GitHub issue, discussion or pull request.
Report it privately on GitHub: Report a vulnerability. For instructions, see Privately reporting a security vulnerability.
Alternatively, report it to the IBM Product Security Incident Response Team (PSIRT) using one of the methods on the IBM Trust Center.
Include in the report:
- The
aspera-cliversion:ascli -v - The Ruby version:
ruby -v - The operating system name and version
- The steps to reproduce, or a proof of concept
- The expected impact
Remove secrets (passwords, tokens, private keys) from logs and configuration files before you send them.
- The report is acknowledged within 14 days.
- It is assessed with the Scope and the Trust Model: the reporter is told whether it is accepted, and why if it is not.
- An accepted vulnerability is fixed in the next release, see Supported Versions. The reporter is asked not to disclose it before this release.
- The release notes (CHANGELOG.md) describe the fix in section "Issues Fixed", with the CVE identifier when one is assigned. They credit the reporter, with the name the reporter chooses, unless the reporter asks to remain anonymous.
- Disclosure:
- A report sent on GitHub is handled in a private GitHub security advisory. After the release, the advisory is published with the fixed version, so that it is in the GitHub Advisory Database.
- A report sent to IBM PSIRT is disclosed by IBM PSIRT (CVE, security bulletin). A GitHub security advisory is published with the same information.
In scope: the Ruby gem aspera-cli (the ascli command), and how it interacts with IBM Aspera components.
See Scope of Support.
Out of scope:
- Vulnerabilities in the IBM Aspera products themselves (
ascp, Transfer SDK, High-Speed Transfer Server, Faspex, Shares, Console, Orchestrator, Aspera on Cloud) and in IBM Cloud Object Storage: report them to IBM PSIRT. - A public CVE in a dependency gem that already has a fixed version: dependencies are updated with Renovate, and the update is included in the next release.
Trusted: the user account that runs ascli, its environment variables, and its configuration file and presets.
ascli restricts access to its configuration file to the current user, and can store secrets in a vault: see Secret Vault.
Commands and options are trusted only at security level low, the default: see Security Level.
- At level
low,asclican do anything that the user is allowed to do: features that execute code or access local files (for example@ruby:,@file:, plugins) work as designed. - At levels
mediumandhigh, commands and options can come from an untrusted client, for example an MCP client.
ascli is not intended to be a public-facing web server.
The web servers that some commands start listen on a loopback address by default, and refuse to listen on another address without their protection: see Web service.
In scope:
- At levels
mediumandhigh: a command or option that bypasses the restrictions of the level, for example to read a file outsideallowed_paths, write a file outsidewritable_paths, execute code, or reveal a secret. - At any level: an issue that a party other than the local user can exploit, for example through a server response, a file received in a transfer, or a position on the network path when TLS certificate verification is enabled.
Out of scope:
- A feature that works as designed at level
low. - An issue that requires the user to disable a protection, for example
--insecure=yes. - A web server of
ascliexposed to users or networks that are not trusted, without the protection of its command, or with HTTP instead of HTTPS on a network.
The security requirements, the threat model, the trust boundaries, and the weaknesses countered are described in docs/ASSURANCE_CASE.md.