ID CVE-2014-8687
Summary Seagate Business NAS devices with firmware before 2015.00322 allow remote attackers to execute arbitrary code with root privileges by leveraging use of a static encryption key to create session tokens.
Vulnerable Configurations
  • cpe:2.3:o:seagate:business_nas_firmware:2014.00319
  • cpe:2.3:h:seagate:business_nas
Base: 10.0
  • Encryption Brute Forcing
    An attacker, armed with the cipher text and the encryption algorithm used, performs an exhaustive (brute force) search on the key space to determine the key that decrypts the cipher text to obtain the plaintext.
  • Creating a Rogue Certificate Authority Certificate
    An attacker exploits a weakness in the MD5 hash algorithm (weak collision resistance) to generate a certificate signing request (CSR) that contains collision blocks in the "to be signed" part. The attacker specially crafts two different, but valid X.509 certificates that when hashed with the MD5 algorithm would yield the same value. The attacker then sends the CSR for one of the certificates to the Certification Authority which uses the MD5 hashing algorithm. That request is completely valid and the Certificate Authority issues an X.509 certificate to the attacker which is signed with its private key. An attacker then takes that signed blob and inserts it into another X.509 certificate that the attacker generated. Due to the MD5 collision, both certificates, though different, hash to the same value and so the signed blob works just as well in the second certificate. The net effect is that the attackers' second X.509 certificate, which the Certification Authority has never seen, is now signed and validated by that Certification Authority. To make the attack more interesting, the second certificate could be not just a regular certificate, but rather itself a signing certificate. Thus the attacker is able to start their own Certification Authority that is anchored in its root of trust in the legitimate Certification Authority that has signed the attackers' first X.509 certificate. If the original Certificate Authority was accepted by default by browsers, so will now the Certificate Authority set up by the attacker and of course any certificates that it signs. So the attacker is now able to generate any SSL certificates to impersonate any web server, and the user's browser will not issue any warning to the victim. This can be used to compromise HTTPS communications and other types of systems where PKI and X.509 certificates may be used (e.g., VPN, IPSec) .
  • Signature Spoof
    An attacker generates a message or datablock that causes the recipient to believe that the message or datablock was generated and cryptographically signed by an authoritative or reputable source, misleading a victim or victim operating system into performing malicious actions.
  • Cryptanalysis
    Cryptanalysis is a process of finding weaknesses in cryptographic algorithms and using these weaknesses to decipher the ciphertext without knowing the secret key (instance deduction). Sometimes the weakness is not in the cryptographic algorithm itself, but rather in how it is applied that makes cryptanalysis successful. An attacker may have other goals as well, such as: 1. Total Break - Finding the secret key 2. Global Deduction - Finding a functionally equivalent algorithm for encryption and decryption that does not require knowledge of the secret key. 3. Information Deduction - Gaining some information about plaintexts or ciphertexts that was not previously known 4. Distinguishing Algorithm - The attacker has the ability to distinguish the output of the encryption (ciphertext) from a random permutation of bits The goal of the attacker performing cryptanalysis will depend on the specific needs of the attacker in a given attack context. In most cases, if cryptanalysis is successful at all, an attacker will not be able to go past being able to deduce some information about the plaintext (goal 3). However, that may be sufficient for an attacker, depending on the context.
exploit-db via4
  • description Seagate Business NAS Unauthenticated Remote Command Execution. CVE-2014-8687. Remote exploit for php platform
    file exploits/php/remote/36264.rb
    id EDB-ID:36264
    last seen 2016-02-04
    modified 2015-03-04
    platform php
    port 80
    published 2015-03-04
    reporter metasploit
    title Seagate Business NAS Unauthenticated Remote Command Execution
    type remote
  • description Seagate Business NAS <= 2014.00319 - Pre-Authentication Remote Code Execution (0day). CVE-2014-8687. Webapps exploit for hardware platform
    file exploits/hardware/webapps/
    id EDB-ID:36202
    last seen 2016-02-04
    modified 2015-03-01
    platform hardware
    port 80
    published 2015-03-01
    reporter OJ Reeves
    title Seagate Business NAS <= 2014.00319 - Pre-Authentication Remote Code Execution 0day
    type webapps
metasploit via4
description Some Seagate Business NAS devices are vulnerable to command execution via a local file include vulnerability hidden in the language parameter of the CodeIgniter session cookie. The vulnerability manifests in the way the language files are included in the code on the login page, and hence is open to attack from users without the need for authentication. The cookie can be easily decrypted using a known static encryption key and re-encrypted once the PHP object string has been modified. This module has been tested on the STBN300 device.
last seen 2019-03-22
modified 2017-07-24
published 2015-03-01
reliability Normal
reporter Rapid7
title Seagate Business NAS Unauthenticated Remote Command Execution
packetstorm via4
refmap via4
bid 72831
  • 36202
  • 36264
Last major update 08-06-2017 - 12:29
Published 08-06-2017 - 12:29
Last modified 16-06-2017 - 13:40
Back to Top