dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 17 Nov 2021. Known ransomware use
FtaApplication · Accellion

CVE-2021-27102

HIGH · 7.8 CVSS v3.1 Published 2021-02-16
Fix available
A fix is available. Upgrade to after 9_12_411 or later.
See remediation →
96/100
Remediation priority · Urgent
In the wild Ransomware 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
Accellion FTA 9_12_411 and earlier is affected by OS command execution via a local web service call. The fixed version is FTA_9_12_416 and later.

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 confidence

Accellion FTA versions 9_12_411 and earlier contains an OS command injection vulnerability in a local web service component, allowing authenticated attackers to execute arbitrary operating system commands. The vulnerability is fixed in version FTA_9_12_416.

MitigationUpgrade the Accellion FTA appliance to version FTA_9_12_416 or later to remediate this command injection vulnerability.

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
FtaApplication
Affected:<= 9_12_411

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Confirm Accellion FTA installation
    Identify Accellion FTA presence in the environment by searching for FTA-related processes, services, or installed packages. Common locations include /opt/accellion or /home/fta. Use 'ps aux | grep -i accellion' or check installed software listings.
    Affected if Accellion FTA software is found running or installed on the system
  2. Determine installed FTA version
    Locate the FTA version file or banner. Common paths include /opt/accellion/fta_version, /home/fta/VERSION, or check the admin web interface login page source. Use 'cat /opt/accellion/fta_version' or similar commands to retrieve the version number.
    Affected if The version cannot be determined or shows as 9_12_411 or earlier
  3. Compare version against affected range
    Parse the version string and compare numerically. Version format is typically 9_12_XXX where XXX is the build number. Versions 9_12_0 through 9_12_411 are all affected.
    Affected if Installed version is 9_12_411 or any earlier version (9_12_410, 9_12_400, etc.)
  4. Check web service exposure
    Examine if the FTA web interface (port 443, 8443, or HTTP port 80) is accessible. Review network configuration to determine if local web services handling admin or file transfer functions are exposed. Check /etc/httpd/conf.d/ for FTA virtual host configurations.
    Affected if The FTA web administration interface is accessible and version is within affected range

If Accellion FTA is installed and the version is 9_12_411 or earlier, the system is affected by this command injection vulnerability and should be investigated further.

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 a release after 9_12_411
Interim mitigation

Upgrade the Accellion FTA appliance to version FTA_9_12_416 or later to remediate this command injection vulnerability.

Recommended fix High confidence

FTA_9_12_416 or later

  1. 1. Identify the current version of Accellion FTA by accessing the admin interface or checking system information
  2. 2. If the current version is FTA 9_12_411 or earlier, plan an upgrade to FTA_9_12_416 or later
  3. 3. Review Accellion's official upgrade documentation and release notes for FTA_9_12_416
  4. 4. Perform a backup of current FTA configuration and data before upgrading
  5. 5. Execute the upgrade process following Accellion's documented upgrade procedure
  6. 6. After upgrade, verify the new version is FTA_9_12_416 or later
  7. 7. Test critical file transfer functionality to ensure the upgrade was successful

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

Fix this in Fta Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,620
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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