dbcve.org
OtterApplication · Inedo

CVE-2017-15607

CRITICAL · 9.8 CVSS v3.0 Published 2017-12-01
Fix available
A fix is available. Upgrade to 1.7.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Inedo Otter before 1.7.4 has directory traversal in filesystem-based rafts via vectors involving '/' characters or initial '.' characters, aka OT-181.

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

A directory traversal vulnerability exists in Inedo Otter's filesystem-based raft functionality. Attackers can manipulate file paths using '/' or initial '.' characters to access files outside the intended directory boundaries, potentially exposing sensitive system files. The critical CVSS score of 9.8 indicates this is remotely exploitable with no authentication required.

MitigationUpgrade Inedo Otter to version 1.7.4 or later to obtain the patch. If immediate upgrade is not feasible, implement strict input validation and path sanitization on all filesystem raft operations to prevent path traversal characters.

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
OtterApplication
Affected:< 1.7.4

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

CVSS:3.0/AV:N/AC:L/PR:N/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. Determine Inedo Otter installed version
    Locate the Otter installation directory and check the product version file, or use the Otter administration interface to view the installed version number.
    Affected if The installed version is lower than 1.7.4
  2. Identify raft storage type in use
    Examine the Otter configuration files or administration settings to determine which raft storage provider is configured. Look for settings related to 'filesystem', 'file-based', or 'raft' storage configuration.
    Affected if The system is configured to use filesystem-based raft storage
  3. Locate raft storage configuration path
    In the Otter configuration or database settings, find the configured path or directory used for filesystem-based raft storage. This is typically specified in a configuration file or database entry defining the raft provider.
    Affected if A filesystem path is configured for raft storage
  4. Review access controls on raft storage directory
    Inspect file system permissions on the configured raft storage directory to determine if untrusted users could supply or manipulate file path inputs.
    Affected if The raft storage directory allows write access from untrusted or remote users who could inject path traversal sequences

A user is affected if their installed Inedo Otter version is below 1.7.4 AND they are using filesystem-based raft storage with accessible configuration that permits path manipulation.

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

Upgrade Inedo Otter to version 1.7.4 or later to obtain the patch. If immediate upgrade is not feasible, implement strict input validation and path sanitization on all filesystem raft operations to prevent path traversal characters.

Recommended fix High confidence

1.7.4 or later

  1. Back up your current Otter installation, configuration files, and database before upgrading
  2. Stop the Otter service
  3. Download Otter version 1.7.4 or later from the official Inedo website (inedo.com)
  4. Install the new version following Inedo's standard upgrade procedure for your deployment method
  5. Start the Otter service
  6. Verify the installation was successful by checking the version number in the UI or via command line
  7. Confirm the path traversal vulnerability (OT-181) is resolved by testing that filesystem-based raft operations no longer accept '../' or initial '.' path sequences
Caveat Minor version upgrades in Otter typically maintain backward compatibility; review Inedo release notes for any configuration changes

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

Fix this in Otter Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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