CVE-2008-3703 in the critical feed json
The management console in the Volume Manager Scheduler Service (aka VxSchedService.exe) in Symantec Veritas Storage Foundation for Windows…
published 2008-08-18 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-3689
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 12.2%
- EPSS 12.2% chance of exploitation in 30 days, percentile 96%
- public exploits
- 0
- none known
Summary
The management console in the Volume Manager Scheduler Service (aka VxSchedService.exe) in Symantec Veritas Storage Foundation for Windows (SFW) 5.0, 5.0 RP1a, and 5.1 accepts NULL NTLMSSP authentication, which allows remote attackers to execute arbitrary code via requests to the service socket that create "snapshots schedules" registry values specifying future command execution. NOTE: this issue exists because of an incomplete fix for CVE-2007-2279.
Patch / fix
Exploit prediction
12.25% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
seer.entsupport.symantec.com
/docs/306386.htm
patch
-
secunia.com
/advisories/31486
third-party-advisory, vendor-advisory
-
securityfocus.com
/archive/1/495481
mailing-list
- zerodayinitiative.com /advisories/ZDI-08-053/
- symantec.com /avcenter/security/Content/2008.08.14a.html
-
securityfocus.com
/bid/30596
vdb-entry
-
vupen.com
/english/advisories/2008/2395
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/44466
vdb-entry
-
securityreason.com
/securityalert/4161
third-party-advisory
-
securityfocus.com
/archive/1/495487/100/0/threaded
mailing-list
-
securitytracker.com
/id?1020699
vdb-entry
Sources
- CVE List CVE-2008-3703
- NVD CVE-2008-3703
Fencer Vulns 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.