dbcve.org
Goflex SatteliteHardware / appliance · Seagate

CVE-2015-2875

HIGH · 7.5 CVSS v3.0 Published 2015-12-31
Fix available
A fix is available. Upgrade to after 2.3.0.014 or later.
See remediation →
84/100
Remediation priority · High
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
Absolute path traversal vulnerability on Seagate GoFlex Satellite, Seagate Wireless Mobile Storage, Seagate Wireless Plus Mobile Storage, and LaCie FUEL devices with firmware before 3.4.1.105 allows remote attackers to read arbitrary files via a full pathname in a download request during a Wi-Fi session.

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

Absolute path traversal vulnerability in the web interface of Seagate GoFlex Satellite, Seagate Wireless Mobile Storage, Seagate Wireless Plus Mobile Storage, and LaCie FUEL devices allows remote attackers to read arbitrary files on the device filesystem by providing full absolute file paths in download requests during Wi-Fi sessions.

MitigationUpdate firmware to version 3.4.1.105 or later. If patching is not possible, isolate the device Wi-Fi network and restrict access to trusted users only.

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
Goflex SatteliteHardware / appliance
Affected:all versions
Wireless Mobile StorageHardware / appliance
Affected:all versions
Wireless Plus Mobile StorageHardware / appliance
Affected:all versions
Lac9000436u FirmwareOperating system
Affected:<= 2.3.0.014
Lac9000464u FirmwareOperating system
Affected:<= 2.3.0.014

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
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/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 Seagate or LaCie wireless storage devices on your network
    Scan your network for devices with HTTP services on common ports (80, 8080) and check the device model through the web interface login page or network discovery. Look for device names containing 'GoFlex', 'Wireless', 'Satellite', or 'FUEL' in the HTTP server banner or web UI.
    Affected if A Seagate GoFlex Satellite, Seagate Wireless Mobile Storage, Seagate Wireless Plus Mobile Storage, or LaCie FUEL device is found on your network and accessible via Wi-Fi.
  2. Check the device firmware version
    Access the device web interface (typically at an IP address on your Wi-Fi network) and navigate to the Settings or About page to view the firmware version. Alternatively, inspect HTTP responses or firmware update endpoints for version information.
    Affected if The firmware version is 2.3.0.014 or earlier for LaCie devices, or any version for Seagate devices (all versions affected).
  3. Confirm the device is accessible via Wi-Fi
    Ensure you are connected to the device's Wi-Fi network or have network access to the device's web interface. The vulnerability is exploitable during Wi-Fi sessions.
    Affected if The device web interface is reachable over Wi-Fi on your network.
  4. Test for absolute path traversal vulnerability (optional confirmation)
    Using a web browser or HTTP tool, send a request to the download endpoint with an absolute path such as /download?file=/etc/passwd or similar path structure used by the device. Compare your installed version to the affected ranges provided.
    Affected if The device returns file contents from the requested absolute path, confirming the path traversal vulnerability exists.

You are affected if a Seagate GoFlex Satellite, Seagate Wireless Mobile Storage, Seagate Wireless Plus Mobile Storage, or LaCie FUEL device with firmware <= 2.3.0.014 (or any version for Seagate products) is accessible on your network via Wi-Fi.

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.

From vendor data
Upgrade available Upgrade to a release after 2.3.0.014
Interim mitigation

Update firmware to version 3.4.1.105 or later. If patching is not possible, isolate the device Wi-Fi network and restrict access to trusted users only.

Fix this in Goflex Sattelite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
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,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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