Goanywhere Managed File TransferApplication · Helpsystems

CVE-2021-46830

MEDIUM · 6.5 CVSS v3.1 Published 2022-07-27
Fix available
A fix is available. Upgrade to 6.8.3 or later.
See remediation →
71/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
A path traversal vulnerability exists within GoAnywhere MFT before 6.8.3 that utilize self-registration for the GoAnywhere Web Client. This vulnerability could potentially allow an external user who self-registers with a specific username and/or profile information to gain access to files at a higher directory level than intended.

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

A path traversal vulnerability in GoAnywhere MFT's self-registration feature for the Web Client (versions before 6.8.3) allows externally registering users to access files outside their intended directory scope by using specially crafted usernames or profile information to manipulate file path references.

MitigationUpgrade to GoAnywhere MFT version 6.8.3 or later to obtain the patched version, or disable the self-registration feature if not required in the environment.

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
Goanywhere Managed File TransferApplication
Affected:< 6.8.3

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
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 checks

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

  1. Identify GoAnywhere MFT installation
    Locate the GoAnywhere MFT installation directory and confirm the product is present on the system
    Affected if GoAnywhere MFT is installed on the system
  2. Check installed GoAnywhere MFT version
    Access the GoAnywhere MFT admin interface or check the product version information, then compare it against the affected range (versions before 6.8.3)
    Affected if The installed version is lower than 6.8.3
  3. Verify Web Client self-registration is enabled
    Access the GoAnywhere MFT administration console, navigate to the Web Client settings, and check whether the self-registration feature is enabled for external users
    Affected if Self-registration is enabled and the version is below 6.8.3
  4. Audit existing user accounts
    Review user accounts created through the self-registration feature, examining usernames and profile information for unusual path characters or patterns (such as ../ sequences)
    Affected if Suspicious usernames or profile data containing path traversal sequences are found

A system is affected if GoAnywhere MFT with a version lower than 6.8.3 is installed AND the Web Client self-registration feature is enabled.

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

Upgrade to GoAnywhere MFT version 6.8.3 or later to obtain the patched version, or disable the self-registration feature if not required in the environment.

Recommended fix High confidence

6.8.3 or later

  1. 1. Backup the current GoAnywhere MFT configuration and database
  2. 2. Download GoAnywhere MFT version 6.8.3 or later from the official GoAnywhere website or your customer portal
  3. 3. Stop the GoAnywhere MFT service before applying the upgrade
  4. 4. Run the installer/upgrade package for version 6.8.3
  5. 5. Follow the on-screen upgrade instructions, preserving existing configuration settings
  6. 6. Start the GoAnywhere MFT service after upgrade completes
  7. 7. Verify the self-registration feature is functioning correctly and test that path traversal is no longer possible
  8. 8. Review user accounts created through self-registration to ensure no malicious accounts exist

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

Fix this in Goanywhere Managed File Transfer Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-46830 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