dbcve.org
Titan Mft ServerApplication · Southrivertech

CVE-2023-45687

HIGH · 8.8 CVSS v3.1 Published 2023-10-16
Fix available
A fix is available. Upgrade to 2.0.18 or later.
See remediation →
95/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges

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 session fixation vulnerability in South River Technologies' Titan MFT and Titan SFTP servers on Linux and Windows allows an attacker to bypass the server's authentication if they can trick an administrator into authorizating a session id of their choosing

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

A detailed technical summary for this CVE is being prepared.

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
Titan Mft ServerApplication
Affected:< 2.0.18
Titan Sftp ServerApplication
Affected:< 2.0.18

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 2.0.18 or later
Fixed in 2.0.18
Recommended fix High confidence

Titan MFT Server 2.0.18 / Titan SFTP Server 2.0.18

  1. 1. Back up the current Titan MFT Server or Titan SFTP Server configuration, including all settings, user accounts, and transfer data.
  2. 2. Download the latest version of Titan MFT Server or Titan SFTP Server version 2.0.18 or later from the South River Technologies vendor site.
  3. 3. Stop the Titan MFT or Titan SFTP service before beginning the upgrade process.
  4. 4. Install version 2.0.18 of the affected product, following the vendor's standard upgrade installation procedures.
  5. 5. After installation, verify that the service starts successfully and all configurations have been preserved.
  6. 6. Test that authentication and session management are functioning correctly, confirming the session fixation vulnerability has been addressed.
  7. 7. Review administrator sessions and consider invalidating any existing sessions as a precautionary measure.

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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