dbcve.org
Wireless Mobile StorageHardware / appliance · Seagate

CVE-2015-2874

CRITICAL · 9.8 CVSS v3.0 Published 2015-12-31
Fix available
A fix is available. Upgrade to after 2.3.0.014 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
Seagate GoFlex Satellite, Seagate Wireless Mobile Storage, Seagate Wireless Plus Mobile Storage, and LaCie FUEL devices with firmware before 3.4.1.105 have a default password of root for the root account, which allows remote attackers to obtain administrative access via a TELNET 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

Seagate GoFlex Satellite, Seagate Wireless Mobile Storage, Seagate Wireless Plus Mobile Storage, and LaCie FUEL devices with firmware versions before 3.4.1.105 contain a hardcoded default password of 'root' for the root account, enabling unauthenticated remote attackers to gain full administrative privileges via TELNET sessions.

MitigationUpdate firmware to version 3.4.1.105 or later to remove the default credential, and disable TELNET access or enforce strong authentication to prevent exploitation.

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
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
Goflex SatteliteHardware / appliance
Affected:all versions

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. Identify the device model
    Check the product label or web interface to confirm the exact model: Seagate Wireless Mobile Storage, Seagate Wireless Plus Mobile Storage, Seagate GoFlex Satellite, or LaCie Lac9000436u/LaCie Lac9000464u
    Affected if The device matches any of these models: Seagate Wireless Mobile Storage, Seagate Wireless Plus Mobile Storage, Seagate GoFlex Satellite, or LaCie Lac9000436u/LaCie Lac9000464u
  2. Verify firmware version
    Access the device web interface or check the firmware version through the administrative settings. For LaCie devices, confirm the firmware version is 2.3.0.014 or earlier
    Affected if The device is a LaCie Lac9000436u or Lac9000464u with firmware version 2.3.0.014 or lower, or any Seagate Wireless/GoFlex model regardless of version
  3. Check if TELNET service is accessible
    Attempt to connect to the device on TELNET port 23 (e.g., telnet <device_ip>) from an authorized network location to see if the service responds
    Affected if TELNET port 23 is open and accepting connections on the device
  4. Test default credential
    If TELNET is accessible, attempt to log in with username 'root' and password 'root' to verify the default credential is active
    Affected if The login succeeds with root/root, indicating the hardcoded password vulnerability is present

The environment is affected if the device is one of the listed models, is accessible via TELNET, and accepts the default root/root credential, which grants full administrative access.

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 2.3.0.014
Interim mitigation

Update firmware to version 3.4.1.105 or later to remove the default credential, and disable TELNET access or enforce strong authentication to prevent exploitation.

Recommended fix High confidence

Firmware version 3.4.1.105 or later

  1. 1. Identify the specific Seagate or LaCie device model from the affected product list
  2. 2. Check the current firmware version on the device through its web interface or admin panel
  3. 3. Navigate to the official Seagate or LaCie support website and locate the firmware download section for your specific device
  4. 4. Download firmware version 3.4.1.105 or later (the fixed release) for your device model
  5. 5. Follow the vendor-provided instructions to apply the firmware update (typically via web UI or USB connection)
  6. 6. After firmware update completes, verify the device is running the new firmware version
  7. 7. Access the device admin interface and change the default root password to a strong, unique password
Caveat Firmware updates may reset device configurations; backup settings before updating if possible

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

Fix this in Wireless Mobile Storage 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-2874 — 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-2874 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