Vulnerability in Symantec Enterprise Vault (EV) for File System Archiving (CVE-2013-1609)
Summary
Vulnerability in Symantec Enterprise Vault (EV) for File System Archiving (CVE-2013-1609). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
Multiple unquoted Windows search path vulnerabilities in the (1) File Collector and (2) File PlaceHolder services in Symantec Enterprise Vault (EV) for File System Archiving before 9.0.4 and 10.x before 10.0.1 allow local users to gain privileges via a Trojan horse program.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2013-1609 has been found in Symantec Enterprise Vault (EV) for File System Archiving.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Symantec Enterprise Vault (EV) for File System Archiving CVE-2013-1609" on the vendor's site.
CVE-2013-1609 (Symantec Enterprise Vault (EV) for File System Archiving)
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in Symantec Enterprise Vault (EV) for File System Archiving.
Check the vendor advisory for the affected versions of Symantec Enterprise Vault (EV) for File System Archiving.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Symantec Enterprise Vault (EV) for File System Archiving を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web securityfocus.com
- web symantec.com