Skip to content
Fencer Intel
critical 9.8

CVE-2014-8687 in the critical feed json

Seagate Business NAS devices with firmware before 2015.00322 allow remote attackers to execute arbitrary code with root privileges by lever…

published 9y ago modified 4mo ago also EUVD-2014-8519

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
43.8%
EPSS 43.8% chance of exploitation in 30 days, percentile 98%
public exploits
3
Metasploit and Exploit-DB

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.

Is CVE-2014-8687 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (Metasploit exploit/linux/http/seagate_nas_php_exec_noauth)
  2. Published

Exploit prediction

43.81% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Metasploit exploit/linux/http/seagate_nas_php_exec_noauth Seagate Business NAS Unauthenticated Remote Command Execution metasploit exploit, normal rank, 2015-03-01
  • EDB-36264 Seagate Business NAS - Remote Command Execution (Metasploit) remote, 2015-03-04
  • EDB-36202 Seagate Business NAS 2014.00319 - Remote Code Execution webapps, 2015-03-01
  • packetstormsecurity.com http://packetstormsecurity.com/files/130609/Seagate-Business-NAS-Unauthenticated-Remote-Command-Execution.html referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/130585/Seagate-Business-NAS-2014.00319-Remote-Code-Execution.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-327 Use of a Broken or Risky Cryptographic Algorithm

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.