What it is
CVE-2014-3206 is an unauthenticated vulnerability affecting Seagate BlackArmor NAS. Seagate BlackArmor NAS allows remote attackers to execute arbitrary code via the session parameter to...
Vulnerability report
Exploited in the wild
High confidence
Not in CISA KEV
CVE-2014-3206
BlackArmor NAS
Seagate / BlackArmor NAS
- Severity
- CVSS 9.8 · Critical
- Confidence
- High
- Exploit status
- Exploited in the wild
- EPSS
- 51.0%
- First observed
- —
- Last observed
- —
Decision summary
What security teams need to know first
Direct answers before the deeper technical record.
Is it exploited?
Yes. KEVIntel tracks this CVE as a known exploited vulnerability. Confidence is high.
Who is affected?
Seagate / BlackArmor NAS.
What should we do?
Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.
Overview
BlackArmor NAS
Seagate BlackArmor NAS allows remote attackers to execute arbitrary code via the session parameter to localhost/backupmgt/localJob.php or the auth_name parameter to localhost/backupmgmt/pre_connect_check.php.
- Published
- 23 Feb 2018
- Exploitation Reported
- 03 Jun 2026
- Attack vector
- Remote
- Complexity
- Low
- Privileges
- None
- User interaction
- None
Tags
nuclei_scanner
CVE References
- 33159 exploit-db.com · Exploit https://www.exploit-db.com/exploits/33159/
Exploitation evidence
Why KEVIntel marks this CVE as exploited
Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.
Exploited in the wild
The Shadowserver
Independent exploitation attestation added to the KEVIntel record.
Proof of concept available
GitHub
Public scanner or PoC coverage increases practical exploitability.
Known exploited vulnerability sources
Per-source evidence links for KEV attestations are available through the KEVIntel Pro API.
Learn about Pro API access| Source | Added |
|---|---|
| The Shadowserver First | 2025-06-07 00:00 UTC |
Detection
Operational artifacts and observed signals
Make the evidence actionable in scanner, SOC, and edge-control workflows.
Observed signals
- Request targets
- 0
- User-Agents
- 0
Raw values available in Pro and Enterprise.
Scanner coverage
Nuclei template detected 25 Apr 2025.
View Nuclei template (opens in new tab)Virtual patch status
No KEVIntel virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.
Learn about virtual patches →Scanner Artifacts
Scanner and exploit-framework references linked to this CVE.
| Scanner | Reference | Detected |
|---|---|---|
| Nuclei | https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2014/CVE-2014-3206.yaml | 25 Apr 2025 |
Risk and context
Severity, weaknesses, and research context
CVSS v3.0
9.8
Critical
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
51.0%
Weaknesses
All CVSS Scores
CVSS v3.0
9.8
Critical
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS v2.0
10.0
High
AV:N/AC:L/Au:N/C:C/I:C/A:C
Potential Proof of Concepts
These PoCs are unverified and could contain malware. Use at your own risk.
laccart/CVE-2014-3206
github · Created 2024-12-29 20:33:02 UTC · 0 stars
Seagate BlackArmor NAS - Command Injection
nuclei · Created Unknown
Timeline
From disclosure to observed exploitation
-
Added to KEVIntel KEV Feed
High-confidence, third-party attested exploitation
-
Nuclei template available
Scanner coverage available
-
Public PoC available
Public proof-of-concept code published
-
CVE published
Vulnerability disclosed publicly
-
CVE ID reserved
Identifier reserved by the CNA
Pro API
Automate this intelligence
Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.
- Evidence confidence and provenance
- First-party sensor telemetry
- PoC and scanner references
- Affected versions and enrichment
- Automation-ready JSON delivery
GET /api/v2/pro/kevs/CVE-2014-3206
Free JSON includes basic KEV fields{
"cve_id": "CVE-2014-3206",
"confidence": "High",
"cvss_score": 9.8,
"epss_score": 0.51014,
"exploit_status": {
"exploited_in_the_wild": true,
"active_exploitation_observed": false
},
"sensor_telemetry": { "attempts": 0, "sensors": 0 }
}